[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Call for testing: Debian 7.3 PVM AMIs in US East 1

>> >> verified on ['ubuntu'] distros but not on debian distro. It may or
>> >> may not work correctly.
>> The right thing to do is to verify that ssh-import-id works on Debian and then
>> contribute upstream to remove the warning. Or disable the plugin in
>> cloud.cfg.
>> ssh-import-id imports SSH public keys from landscape or other online
>> locations.
> ssh-import-id is not available in Debian stable, and not currently in backports. It is in Jessie and Sid.  Do we want this in the base AMI - if so, do we want to ask for a git hub package (and then wait until 7.4 for this) or do we want to install online? Please express opinions! ;)

Oh. I didn't realize that it requires an external tool. So I'd say
disable it for the moment and fix it (or look into it) for a future
respin of the image. Or wait until users start asking for it before
becoming active :-)

>> >> 2013-12-17 09:20:25,565 - util.py[WARNING]: Running apt-configure
>> >> (<module 'cloudinit.config.cc_apt_configure' from
>> >> '/usr/lib/python2.7/dist-packages/cloudinit/config/cc_apt_configure.p
>> >> yc'>)
>> >> failed
>> Can you post the relevant messages from the cloud-init log?
> Dec 18 08:11:04 ip-10-36-77-183 [CLOUDINIT] util.py[WARNING]: Running apt-configure (<module 'cloudinit.config.cc_apt_configure' from '/usr/lib/python2.7/dist-packages/
> cloudinit/config/cc_apt_configure.pyc'>) failed
> Dec 18 08:11:04 ip-10-36-77-183 [CLOUDINIT] util.py[DEBUG]: Running apt-configure (<module 'cloudinit.config.cc_apt_configure' from '/usr/lib/python2.7/dist-packages/cloudinit/config/cc_apt_configure.pyc'>) failed#012Traceback (most recent call last):#012  File "/usr/lib/python2.7/dist-packages/cloudinit/stages.py", line 553, in _run_modules#012    cc.run(run_name, mod.handle, func_args, freq=freq)#012  File "/usr/lib/python2.7/dist-packages/cloudinit/cloud.py", line 63, in run#012    return self._runners.run(name, functor, args, freq, clear_on_fail)#012  File "/usr/lib/python2.7/dist-packages/cloudinit/helpers.py", line 197, in run#012    results = functor(*args)#012  File "/usr/lib/python2.7/dist-packages/cloudinit/config/cc_apt_configure.py", line 64, in handle#012    generate_sources_list(release, mirrors, cloud, log)#012  File "/usr/lib/python2.7/dist-packages/cloudinit/config/cc_apt_configure.py", line 154, in generate_sources_list#012    templater.render_to_file(template_fn, '/etc/apt/sources.list', params)#012  File "/usr/lib/python2.7/dist-packages/cloudinit/templater.py", line 33, in render_to_file#012    contents = render_from_file(fn, params)#012  File "/usr/lib/python2.7/dist-packages/cloudinit/templater.py", line 29, in render_from_file#012    return render_string(util.load_file(fn), params)#012  File "/usr/lib/python2.7/dist-packages/cloudinit/templater.py", line 40, in render_string#012    return Template(content, searchList=[params]).respond()#012  File "cheetah_DynamicallyCompiledCheetahTemplate_1387354264_29_81928.py", line 114, in respond#012NotFound: cannot find 'security'

Looks like the rendering of the apt.sources file fails. Can yo point
me to your cloud-init package and the cloud.cfg file that you're

> Question for the community: byobu: disable from cloud.cfg, or install in the base AMI?

I strongly advise against enabling byobu. Ubuntu had it enabled by
default when it became available and we (HP Cloud) got a lot of user
requests to disable this thing. Ubuntu eventually realized that it was
a mistake and it's now disabled in all of their images.


>   James

Reply to: