Thank you @patriciasd for the bug. I can confirm failure path reproducer in cloud-init-base.postinst when upgrading systems which have set a debconfig multi-line value for cloud- init/local-cloud-config.
In practice, this is only set in certain MAAS environments MAAS server < 3.5 and upgrades from cloud-init in Plucky to Questing. I'll have a PPA up to allow testing prior to SRU to questing. We also will add separate integration-test coverage in cloud-init's existing testing to preseed known MAAS debconf settings in order to better exercise this postinst path in the future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127022 Title: upgrade from Plucky to Questing cloud-init-base 25.3~2g890873f5-0ubuntu2 failed to install/upgrade on MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2127022/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
