stack trace if 'local-hostname' is not in meta-data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
High
|
Scott Moser | ||
Oneiric |
Fix Released
|
High
|
Scott Moser |
Bug Description
This is most likely an issue for OVF or cmdline seeding of the 'nocloud' data source, as openstack, eucalyptus and ec2 will have 'local-hostname' in the metadata and will not hit this.
However, it basically prevents this from functioning for OVF or cmdline seeding.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: cloud-init 0.6.1-0ubuntu19
ProcVersionSign
Uname: Linux 3.0.0-11-virtual i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Fri Sep 23 13:12:29 2011
Ec2AMI: ami-00000094
Ec2AMIManifest: FIXME
Ec2Availability
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
PackageArchitec
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu20
---------------
cloud-init (0.6.1-0ubuntu20) oneiric; urgency=low
* fix broken path if local-hostname was not in metadata (LP: #857380)
* redirect output of 'start networking' in 'cloud-init-nonet' to /dev/null
* include GPLv3 in source tree
-- Scott Moser <email address hidden> Fri, 23 Sep 2011 09:24:27 -0400