[Bug 2084444] Re: juju can not parse new 50-cloud-init.yaml properly after netplan 0.107 under 22.04

[Lukas Märdian]

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: netplan.io (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Tags added: block-proposed-jammy

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: juju (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: netplan
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/2084444

Title:
  juju can not parse new 50-cloud-init.yaml properly after netplan 0.107
  under 22.04

Status in Netplan:
  Won't Fix
Status in cloud-init package in Ubuntu:
  New
Status in juju package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in cloud-init source package in Jammy:
  New
Status in juju source package in Jammy:
  New
Status in netplan.io source package in Jammy:
  New

Bug description:
  Ubuntu 22.04
  netplan - 0.107.1-3ubuntu0.22.04.1
  juju - 3.5.4

  It looks like there is a regression with new netplan 0.107 version
  under 22.04. Now juju can not start lxd containers due to following
  error:

  2024-10-12 09:10:24 ERROR juju.worker.lxdprovisioner provisioner_task.go:1304 cannot start instance for machine "7/lxd/3": failed to bridge devices: bridge activation error: yaml: unmarshal errors:
    line 10: cannot unmarshal !!str 0 into int
    line 12: cannot unmarshal !!str 100 into int
    line 15: cannot unmarshal !!str 0 into int
    line 32: cannot unmarshal !!str 0 into int
    line 34: cannot unmarshal !!str 100 into int
    line 37: cannot unmarshal !!str 0 into int
    line 53: cannot unmarshal !!str 15 into int
    line 112: field openvswitch not found in type netplan.VLAN
    line 126: field openvswitch not found in type netplan.VLAN
    line 140: field openvswitch not found in type netplan.VLAN
    line 154: field openvswitch not found in type netplan.VLAN
    line 161: field openvswitch not found in type netplan.VLAN
    line 168: field openvswitch not found in type netplan.VLAN

  The generated netplan is following:

  https://pastebin.canonical.com/p/ZfGfCvRx5d/

  It looks like  new netplan renders network config configuration
  received from maas cloud-init differently then previous version.

  To allow lxc container creation following changes had to be done to the netplan file:
  1) Change string values to int values:

  mii-monitor-interval: "100"  -> 100
  up-delay: "0" -> 0
  down-delay: "0" -> 0

  2) Comment out openvswitch: {} from the vlan definition:

  br-data.3219:
        addresses:

    - "X.X.X.X/X"
    mtu: 9000
    id: 3219
    link: "br-data"
  # openvswitch: {}

  So there seems to be 2 problems:
  1) string vs int value types in netplan are not handled properly
  2) "openvswitch" component is now explicitely writen to the netplan and juju parser can not validate it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2084444/+subscriptions