[Bug 1997467] Re: Update 0.105-0ubuntu2~22.04.1 seems to cause regressions with snapd integration

[Lukas Märdian]

I've prepared something here:
https://github.com/canonical/netplan/pull/299

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

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

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

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

-- 
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/1997467

Title:
  Update 0.105-0ubuntu2~22.04.1 seems to cause regressions with snapd
  integration

Status in netplan:
  Triaged
Status in netplan.io package in Ubuntu:
  New
Status in netplan.io source package in Jammy:
  New
Status in netplan.io source package in Kinetic:
  New
Status in netplan.io source package in Lunar:
  New

Bug description:
  Sorry that this is a bit unspecific right now, I will try to provide
  more details ASAP.

  We see failures in our nested core20-early-config test, e.g.
  https://github.com/snapcore/snapd/actions/runs/3512986269/jobs/5885568960

  The test fails in the following place:
  """
  ...
  + remote.exec 'sudo snap set system system.network.netplan.network.bridges.br54.dhcp4=false'
  + MATCH false
  + remote.exec sudo 'netplan get bridges.br54.dhcp4'
  grep error: pattern not found, got:
  true
  """
  at this point the files look like this (sudo is now needed which was not before btw):
  """
  $ sudo cat /etc/netplan/0-snapd-defaults.yaml 
  network:
    version: 2
    ethernets:
      ens3:
        addresses:
        - "10.0.2.15/24"
        dhcp4: false
        routes:
        - to: "default"
          via: "10.0.2.2"
    bridges:
      br54:
        dhcp4: true

  $ sudo cat /etc/netplan/50-cloud-init.yaml 
  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
      ethernets:
          enp0s2:
              dhcp4: true
              match:
                  macaddress: '52:54:00:12:34:56'
              set-name: enp0s2
      version: 2
  """
  When I manually run 

     $ sudo snap set system
  system.network.netplan.network.bridges.br54.dhcp4=false

  inside the VM I see no error but the file 0-snapd-defaults.yaml is unchanged and no
  new file 90-snapd-config is created. The logic inside snapd is that the gadget defaults
  are stored as 0-snapd-defaults and later changes are stored in 90-sanpd-config so that
  the later config values win over the earlier ones.

  Fwiw, this test is also run on a core20 system with netplan 104 and
  there the same test works succesfully afaict.

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