[Bug 1768802] [NEW] netplan try: ethernet device not reverted

[Daniel Axtens]

Public bug reported:

I have an ethernet device, with an MTU of 1500:

ubuntu at netplan:~$ ip l
...
3: ens8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 52:54:00:f9:e9:dd brd ff:ff:ff:ff:ff:ff

I try the following config, 1-mtu.yaml:

network:
    version: 2
    ethernets:
        ens8:
            match:
                macaddress: 52:54:00:f9:e9:dd
            addresses:
               - 10.10.10.2/24
            mtu: 1280


I then do netplan try and let it time out and reset:

ubuntu at netplan:~$ sudo netplan try --timeout 10 --config 1-mtu.yaml
Warning: Stopping systemd-networkd.service, but it can still be activated by:
  systemd-networkd.socket
Do you want to keep these settings?


Press ENTER before the timeout to accept the new configuration


Changes will revert in  1 seconds
Reverting.
Warning: Stopping systemd-networkd.service, but it can still be activated by:
  systemd-networkd.socket

I then observe that the device has in no way been reverted: it's still
up, has the IP and the MTU. To add insult to injury, it's been renamed
to eth0:

ubuntu at netplan:~$ ip a
...
5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:f9:e9:dd brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.2/24 brd 10.10.10.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fef9:e9dd/64 scope link 
       valid_lft forever preferred_lft forever

I have tested this with virtio and rtl8139 devices in a KVM guest; both
exhibit exactly the same behaviour.

** Affects: netplan.io (Ubuntu)
     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/1768802

Title:
  netplan try: ethernet device not reverted

Status in netplan.io package in Ubuntu:
  New

Bug description:
  I have an ethernet device, with an MTU of 1500:

  ubuntu at netplan:~$ ip l
  ...
  3: ens8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
      link/ether 52:54:00:f9:e9:dd brd ff:ff:ff:ff:ff:ff

  I try the following config, 1-mtu.yaml:

  network:
      version: 2
      ethernets:
          ens8:
              match:
                  macaddress: 52:54:00:f9:e9:dd
              addresses:
                 - 10.10.10.2/24
              mtu: 1280

  
  I then do netplan try and let it time out and reset:

  ubuntu at netplan:~$ sudo netplan try --timeout 10 --config 1-mtu.yaml
  Warning: Stopping systemd-networkd.service, but it can still be activated by:
    systemd-networkd.socket
  Do you want to keep these settings?

  
  Press ENTER before the timeout to accept the new configuration

  
  Changes will revert in  1 seconds
  Reverting.
  Warning: Stopping systemd-networkd.service, but it can still be activated by:
    systemd-networkd.socket

  I then observe that the device has in no way been reverted: it's still
  up, has the IP and the MTU. To add insult to injury, it's been renamed
  to eth0:

  ubuntu at netplan:~$ ip a
  ...
  5: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UP group default qlen 1000
      link/ether 52:54:00:f9:e9:dd brd ff:ff:ff:ff:ff:ff
      inet 10.10.10.2/24 brd 10.10.10.255 scope global eth0
         valid_lft forever preferred_lft forever
      inet6 fe80::5054:ff:fef9:e9dd/64 scope link 
         valid_lft forever preferred_lft forever

  I have tested this with virtio and rtl8139 devices in a KVM guest;
  both exhibit exactly the same behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1768802/+subscriptions