yahoo-eng-team team mailing list archive

[James Falcon <1513142@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/2595

** Bug watch added: github.com/canonical/cloud-init/issues #2595
   https://github.com/canonical/cloud-init/issues/2595

** Changed in: cloud-init
       Status: Confirmed => Expired

-- 
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/1513142

Title:
  cloud-init ignores configured cloud_dir for status.json and
  result.json data

Status in cloud-init:
  Expired

Bug description:
  Somewhere between cloud-init-0.7.4 and cloud-init-0.7.5, the cloud-
  init runtime was refactored a bit so that certain cloud-init data is
  dropped statically into certain locations (/var/lib/cloud/data and
  /run/cloud-init) rather than locations in the configured cloud_dir.

  The particular problem crops up in the 'status_wrapper' function in
  the cloud-init runtime -- although the function accepts arguments for
  the 'data dir' and the 'link dir' (/var/lib/cloud/data and /run/cloud-
  init respectively), the actual CLI does not pass any arguments (nor
  does it allow the user to pass arguments either via the CLI or read
  from the cloud.cfg).

  Thus, cloud-init data is scattered in all of the following locations:

  * The configured cloud_dir
  * /var/lib/cloud/data
  * /run/cloud-init

  ...which is contrary to the previous behavior (0.7.4 and prior), where
  everything is co-located in the cloud_dir.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1513142/+subscriptions