Backport cloud-init status --wait to Trusty

Bug #1784901 reported by Adam Collard on 2018-08-01
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)

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.

  Installed: 0.7.5-0ubuntu1.22
  Candidate: 0.7.5-0ubuntu1.22
  Version table:
 *** 0.7.5-0ubuntu1.22 0
        500 trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     0.7.5-0ubuntu1.18 0
        500 trusty-security/main amd64 Packages
     0.7.5-0ubuntu1 0
        500 trusty/main amd64 Packages

Changed in cloud-init (Ubuntu):
assignee: nobody → Chad Smith (chad.smith)
Chad Smith (chad.smith) wrote :

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.

Changed in cloud-init (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Scott Moser (smoser) on 2018-08-07
Changed in cloud-init (Ubuntu Trusty):
status: New → Triaged
importance: Undecided → Wishlist
Changed in cloud-init (Ubuntu):
assignee: Chad Smith (chad.smith) → nobody
Scott Moser (smoser) on 2018-08-07
Changed in cloud-init (Ubuntu):
status: Triaged → Fix Released
Chad Smith (chad.smith) wrote :

This changeset is not as low-hanging as I originally expected. Trusty still sits at 0.7.5 which has no cloudinit.cmd module yet which encapsulates the CLI. This makes backporting the CLI a little bit more than a single file backport and a bit more delta for trusty which we may not be super comfortable with.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers