Enable cloud-init debug output to better support problem analysis
Bug #842488 reported by
Kapil Thangavelu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
Low
|
Scott Moser | ||
juju (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Enabling the cloud-init debug log output would be very helpful to determining any issues while executing cloud-init. As an example of where this would be useful now.. the openstack run of cloud-init takes quite some time to install keys on an instance.
Related branches
lp:~smoser/pyjuju/cloud-init-output-log
- Gustavo Niemeyer: Approve
- Clint Byrum (community): Needs Fixing
-
Diff: 37 lines (+4/-1)3 files modifiedensemble/providers/common/utils.py (+2/-1)
ensemble/providers/orchestra/tests/data/bootstrap_late_command (+1/-0)
ensemble/providers/orchestra/tests/data/launch_late_command (+1/-0)
Changed in ensemble (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in juju: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
linking a bug for the kanban view