Hi Robie, thanks for opening this bug! We discussed covering the "cloud-init installed but disabled" case yesterday at standup, and it would be indeed good to cover it. The question we also discussed how the failure mode we hit compares to any of the other commands/tools called during postinst (or any other stage) failing in a way we didn't account for. And there is a difference: is that cloud-id was not misbehaving, so this is a valid setup to test, and not just one random way a system can be in a broken state.
This said, cloud-id clould probably behave better when there's no instance-data.json, considering it a valid case of cloud-id being "" (empty string). However this has to be discussed on the cloud-init side and can't be considered a fix on the ua side, given that ua doesn't even depend on cloud-init, so we can't "fix" this on the cloud-init side and declare a versioned dependency. On your "fix based implementation detail" comment: that was also brought up by Renan, who has a different fix to propose that takes into account the RC of cloud-id. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938208 Title: No CI testing for the case that cloud-init is installed but not in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1938208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
