ec2metadata fails with traceback within ensemble nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-utils |
Fix Released
|
Medium
|
Unassigned | ||
pyjuju |
Won't Fix
|
Low
|
Unassigned |
Bug Description
On nodes that have been bootstrapped via ensemble, ec2metadata fails with the following traceback:
# ec2metadata
ami-e7c5048e
0
(unknown)
unavailable
us-east-1b
ami
ephemeral0
root
swap
none
i-97e895f6
m1.small
ip-10-72-
10.72.203.28
aki-805ea7e9
12:31:39:24:cb:ee
default-paravirtual
unavailable
ec2-184-
184.73.62.175
Traceback (most recent call last):
File "/usr/bin/
main()
File "/usr/bin/
display(
File "/usr/bin/
value = m.get(metaopt)
File "/usr/bin/
keyids = [ line.split('=')[0] for line in data.splitlines() ]
AttributeError: 'NoneType' object has no attribute 'splitlines'
The following userdata is injected into image via ensemble:
#part-000
#cloud-config
apt-update: true
apt-upgrade: true
apt_sources:
- {source: 'ppa:ensemble/ppa'}
machine-data: {ensemble-
machine-id: 14}
packages: [bzr, tmux, python-setuptools, python-twisted, python-argparse, python-txaws,
python-zookeeper]
runcmd: [sudo apt-get -y install ensemble, sudo mkdir -p /var/lib/ensemble, sudo mkdir
-p /var/log/ensemble, 'ENSEMBLE_
python -m ensemble.
--pidfile=
ssh_authorized_
Related branches
description: | updated |
Changed in cloud-utils: | |
importance: | Undecided → Medium |
status: | New → Fix Committed |
The issue here is that ensemble launches instances with no public key (euca-run-instances --key).
fix coming.