Ubuntu
cloud-init package

status is "not run" instead of "disabled"

Bug #1965275 reported by Valentin David
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Fix Released
High
Unassigned

Bug Description

On 2.1-14-g2e17a0d6-0ubuntu1~22.04.3

`cloud-init status` reports `status: not-run` even though `/usr/lib/systemd/system-generators/cloud-init-generator` has run as generator and marked it as disabled.

The right status which is also what focal gives is `status: disabled`.

`cloud-init status` looks for `/run/cloud-init/disabled`. But this file is never created by anything. Instead it should check for the non-existence of `/run/cloud-init/enabled`.

I have sent a patch to upstream: https://github.com/canonical/cloud-init/pull/1339

But this fix is needed for Ubuntu Core 22. So I hope the fix will be applied soon to the jammy package.

James Falcon (falcojr)
Changed in cloud-init (Ubuntu):
status: New → Triaged
importance: Undecided → High
Revision history for this message
James Falcon (falcojr) wrote :

See https://github.com/canonical/cloud-init/pull/1349

Changed in cloud-init (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
James Falcon (falcojr) wrote :

This was released in cloud-init 22.1.

Changed in cloud-init (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.