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

Bug #1513142 reported by Jon McKenzie on 2015-11-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone

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.

Scott Moser (smoser) on 2016-04-06
Changed in cloud-init:
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers