yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #00262
[Bug 1076811] Re: Cloud-init modules do not reflect loaded config
This bug was fixed in the package cloud-init - 0.7.1-0ubuntu1
---------------
cloud-init (0.7.1-0ubuntu1) raring; urgency=low
* New upstream release.
* landscape: install landscape-client package if not installed.
only take action if cloud-config is present (LP: #1066115)
* landscape: restart landscape after install or config (LP: #1070345)
* multipart/archive: do not fail on unknown headers in multipart
mime or cloud-archive config (LP: #1065116).
* tools/Z99-cloud-locale-test.sh: avoid warning when user's shell is
zsh (LP: #1073077)
* fix stack trace when unknown user-data input had unicode (LP: #1075756)
* split 'apt-update-upgrade' config module into 'apt-configure' and
'package-update-upgrade-install'. The 'package-update-upgrade-install'
will be a cross distro module.
* fix bug where cloud-config from user-data could not affect system_info
settings (LP: #1076811)
* add yum_add_repo configuration module for adding additional yum repos
* fix public key importing with config-drive-v2 datasource (LP: #1077700)
* handle renaming and fixing up of marker names (LP: #1075980)
this relieves that burden from the distro/packaging.
* group config: fix how group members weren't being translated correctly
when the group: [member, member...] format was used (LP: #1077245)
* work around an issue with boto > 0.6.0 that lazy loaded the return from
get_instance_metadata(). This resulted in failure for cloud-init to
install ssh keys. (LP: #1068801)
* add power_state_change config module for shutting down stystem after
cloud-init finishes. (LP: #1064665)
-- Scott Moser <smoser@xxxxxxxxxx> Wed, 14 Nov 2012 15:18:50 -0500
** Changed in: cloud-init (Ubuntu Raring)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1076811
Title:
Cloud-init modules do not reflect loaded config
Status in Init scripts for use on cloud images:
Fix Released
Status in “cloud-init” package in Ubuntu:
Fix Released
Status in “cloud-init” source package in Precise:
Fix Released
Status in “cloud-init” source package in Quantal:
Triaged
Status in “cloud-init” source package in Raring:
Fix Released
Bug description:
After cloud-init consumes its userdata, it continues using the initial
userdata/system config and distro objects, and does not force them to
be reloaded so modules about to be ran (or modules which will use the
distro) will reflect this new data. After the program exits and the
next 'stage' runs that stage though does reload the configuration
correctly. It needs to be fixed for the init stage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1076811/+subscriptions