yahoo-eng-team team mailing list archive

[Chad Smith <1966085@xxxxxxxxxxxxxxxxxx>]

** Also affects: cloud-init (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Jammy)
   Importance: High
       Status: Triaged

** Also affects: cloud-init (Ubuntu Impish)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu Bionic)
       Status: New => In Progress

** Changed in: cloud-init (Ubuntu Focal)
       Status: New => In Progress

** Changed in: cloud-init (Ubuntu Impish)
       Status: New => In Progress

** Changed in: cloud-init (Ubuntu Jammy)
       Status: Triaged => In Progress

** Changed in: cloud-init
     Assignee: (unassigned) => James Falcon (falcojr)

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

Title:
  cloud-init status --wait never returns if datasource not found

Status in cloud-init:
  Triaged
Status in cloud-init package in Ubuntu:
  In Progress
Status in cloud-init source package in Bionic:
  In Progress
Status in cloud-init source package in Focal:
  In Progress
Status in cloud-init source package in Impish:
  In Progress
Status in cloud-init source package in Jammy:
  In Progress

Bug description:
  Calling "cloud-init status --wait" never returns if ds-identify cannot
  find a datasource.

  In https://github.com/canonical/cloud-init/pull/1162, we modified
  status checks to wait until we get an "enabled" or "disabled" file
  from ds-identiy. ds-identify never outputs a "disabled" file, so
  "status --wait" will wait indefinitely if no datasource is found.

  A simple reproduction is to change "ret=1" on this line:
  https://github.com/canonical/cloud-init/blob/main/tools/ds-identify#L1866

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