yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

Just marking this explicitly that it does not affect 12.04/precise.  The
bug was only in 0.7.X series.

** Changed in: cloud-init
       Status: New => Triaged

** Changed in: cloud-init
   Importance: Undecided => High

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Quantal)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu Precise)
   Importance: Undecided => Low

** Changed in: cloud-init (Ubuntu Precise)
       Status: New => 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 Committed
Status in “cloud-init” package in Ubuntu:
  New
Status in “cloud-init” source package in Precise:
  Fix Released
Status in “cloud-init” source package in Quantal:
  New

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