I have a Netplan revert prepared in a PPA and did some testing around it: https://launchpad.net/~slyon/+archive/ubuntu/testing/+packages?field.name_filter=&field.status_filter=published&field.series_filter=jammy
Unfortunately, it won't work as expected, as "apt upgrade" will not remove the new python3-netplan & netplan-generator packages on upgrade (needs "full-upgrade"/"dist-upgrade"). Therefore, the rollback won't reach our users. Furthermore, people that already started using 0.107 functionality (veth,dummy,wpa3,...) would be left stranded with broken network configuration after reverting to 0.106. Due to those new YAML settings not being supported on v0.106. So I don't think a revert is the correct approach here. People using 0.107 from -updates currently should stay on that version. 0.106.1-7ubuntu0.22.04.4 from -security should be restored in jammy-updates and the current version in -updates should be moved back to jammy-proposed. This would allow us to fix the triggering condition in Netplan or cloud- init, or the root-cause in Juju. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084444 Title: juju can not parse new 50-cloud-init.yaml properly after netplan 0.107 under 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/2084444/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
