cloud-init will emit Netplan YAML through libnetplan when the netplan Python module is available (via python3-netplan).
netplan.io 0.107.1 recently backported to Jammy introduces this new package. Some Bond parameters settings were emitted as integers by cloud-init to the YAML file it will create under /etc/netplan. These same settings have always been emitted as strings by libnetplan though. So when cloud-init uses the python3-netplan module to parse and emit the YAML, there will be a change in behavior (settings that were integers are now strings). That is not a problem for netplan though as it will accept both formats. The problem is that Juju has it's own Netplan YAML parser and expects these settings to be integers [1]. As cloud-init will emit them as strings now (because the new netplan 0.107.1 installs python3-netplan), Juju will break. [1] - https://github.com/juju/juju/blob/3.6/network/netplan/netplan.go#L194 -- 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/netplan/+bug/2084444/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
