** Description changed: [ Impact ] There was an upstream change that moved `RequiresMountsFor=/var/lib/cloud` from cloud-init-local.service to cloud-init-main.service. Since cloud-init-main.service was patched out of stable downstreams, this `RequiresMountsFor` line was accidentally removed rather than preserved in cloud-init-local.service. This causes NoCloud to be undetected in some cases (identified when using LVM). The fix is to add `RequiresMountsFor=/var/lib/cloud` back into cloud- init-local.service. [ Test Plan ] - In affected environments, cloud-init should detect NoCloud seed data where it hadn't previously. The issue has not been reproduced by cloud-init devs, but a PPA was provided to the customer with the aforementioned fix: - https://launchpad.net/~holmanb/+archive/ubuntu/cloud-init-test-jammy - - The fix has already been verified to work by the customer: - https://github.com/canonical/cloud-init/issues/6001#issuecomment-2636917095 - - Given the straightforward cause and solution, we believe this is - sufficient to test the fix. + The root cause is that cloud-init runs before /var is mounted and misses + NoCloud data that gets mounted there. To verify the fix, we will analyze + the critical chain on boot and ensure the /var mount is included before + cloud-init-local.service [ Where problems could occur ] The removal allowed cloud-init to start earlier than it had previously. Fixing this means cloud-init may finish slightly later than it had while this bug was present. [ Other Info ] Upstream bug: https://github.com/canonical/cloud-init/issues/6001
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2097441 Title: nocloud detection failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2097441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
