Backport cloud-init status --wait to Trusty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Trusty |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
`cloud-init status --wait` is the canonical way to wait for cloud-init to finish, so things that rely on it's actions can use it and know that they're complete.
It's hard to write such tooling when the Trusty version of cloud-init does not support the 'status --wait' sub-command.
cloud-init:
Installed: 0.7.5-0ubuntu1.22
Candidate: 0.7.5-0ubuntu1.22
Version table:
*** 0.7.5-0ubuntu1.22 0
500 http://
100 /var/lib/
0.
500 http://
0.7.5-0ubuntu1 0
500 http://
Changed in cloud-init (Ubuntu): | |
assignee: | nobody → Chad Smith (chad.smith) |
Changed in cloud-init (Ubuntu Trusty): | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in cloud-init (Ubuntu): | |
assignee: | Chad Smith (chad.smith) → nobody |
Changed in cloud-init (Ubuntu): | |
status: | Triaged → Fix Released |
Should be a faily simple opportunity to backport tooling-only. The CLI is decoupled from the general behavior of cloud-init on clouds and it'd be nice to have both cloud-init collect-logs as well as cloud-init status on earlier LTS than Xenial.