Re: Debian 7.2 EC2 AMIs - now with CloudInit. Removing 7.1a and 7.0.0 AMIs

On Tue, Nov 12, 2013 at 7:49 AM, Chris Fordham <chris@fordham-nagy.id.au> wrote:

On Nov 12, 2013 1:10 AM, "Felipe Reyes" <freyes@tty.cl> wrote:
>
> Hi James,
>
> On Sun, Nov 10, 2013 at 10:33:46AM +0800, James Bromberger wrote:
> > [...]
> > So, without further ado, I'd love to get some further testing of these
> > AMIs before I push to GovCloud and to Marketplace, or return to HVM/S3 AMIs:
> >
> >
> > Region: 32 bit, 64 bit
> > ======================
> > US-East-1: ami-c72379ae, ami-db2278b2
> I gave a try to the new images (specifically ami-db2278b2), I launched a
> m1.large instance inside a VPC, taking a look to the logs I found the
> following lines that caught my attention:
>
> __init__.py[DEBUG]: Seeing if we can get any data from <class 'cloudinit.sources.DataSourceCloudStack.DataSourceCloudStack'>
> DataSourceCloudStack.py[DEBUG]: No lease file found, using default gateway
> util.py[DEBUG]: Reading from /proc/net/route (quiet=False)
> util.py[DEBUG]: Read 512 bytes from /proc/net/route
> DataSourceCloudStack.py[DEBUG]: Found default route, gateway is 172.xx.yy.1
> util.py[DEBUG]: Reading from /var/lib/cloud/seed/cs/meta-data (quiet=False)
> url_helper.py[DEBUG]: [0/1] open 'http://172.xx.yy.1//latest/meta-data/instance-id' with {'url': 'http://172.xx.yy.1//latest/meta-data/instance-id', 'headers': {'User-Agent': 'Cloud-Init/0.7.2'}, 'allow_redirects': True, 'method': 'GET', 'timeout': 50.0} configuration
> url_helper.py[WARNING]: Calling 'http://172.xx.yy.1//latest/meta-data/instance-id' failed [50/120s]: request error [(<urllib3.connectionpool.HTTPConnectionPool object at 0x152cf90>, 'Connection to 172.xx.yy.1 timed out. (connect timeout=50.0)')]
> url_helper.py[DEBUG]: Please wait 1 seconds while we wait to try again
> url_helper.py[DEBUG]: [0/1] open 'http://172.xx.yy.1//latest/meta-data/instance-id' with {'url': 'http://172.xx.yy.1//latest/meta-data/instance-id', 'headers': {'User-Agent': 'Cloud-Init/0.7.2'}, 'allow_redirects': True, 'method': 'GET', 'timeout': 50.0} configuration
> url_helper.py[WARNING]: Calling 'http://172.xx.yy.1//latest/meta-data/instance-id' failed [101/120s]: request error [(<urllib3.connectionpool.HTTPConnectionPool object at 0x1548bd0>, 'Connection to 172.xx.yy.1 timed out. (connect timeout=50.0)')]
> url_helper.py[DEBUG]: Please wait 1 seconds while we wait to try again
> url_helper.py[DEBUG]: [0/1] open 'http://172.xx.yy.1//latest/meta-data/instance-id' with {'url': 'http://172.xx.yy.1//latest/meta-data/instance-id', 'headers': {'User-Agent': 'Cloud-Init/0.7.2'}, 'allow_redirects': True, 'method': 'GET', 'timeout': 17.0} configuration
> url_helper.py[WARNING]: Calling 'http://172.xx.yy.1//latest/meta-data/instance-id' failed [119/120s]: request error [(<urllib3.connectionpool.HTTPConnectionPool object at 0x1548a90>, 'Connection to 172.xx.yy.1 timed out. (connect timeout=17.0)')]
> url_helper.py[DEBUG]: Please wait 1 seconds while we wait to try again
> DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata from ['http://172.xx.yy.1//latest/meta-data/instance-id'] after 120 seconds
>
>
> I'm not sure if those timeout errors are OK, but in any case seems to be
> not OK block the boot up for 2 minutes.
>
> Another problem I found inspecting the logs is this exception (I pretty printed the traceback to make it easier to read):
>
> Nov 11 13:03:42 ip-172-18-10-82 [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_1384175021_96_98085.py", line 114, in respond
> #012 NotFound: cannot find 'security'
>
> All the rest seems to be OK, and my instance is working as far as I checked.
>
> Please let me know if you need additional information, or if you prefer I file
> a ticket to track these issues.
>
> Best Regards,
> --
> Felipe Reyes
> https://github.com/freyes

I also noticed it trying to use the CloudStack data source and was wondering why. I don't think it ran the EC2 data source either.