yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1961803] [NEW] netplan renaming does not work on maas deployed machines on reboot

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Ioanna Alifieraki <1961803@xxxxxxxxxxxxxxxxxx>
Date: Tue, 22 Feb 2022 15:23:42 -0000
Reply-to: Bug 1961803 <1961803@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

Public bug reported:

Netplan renaming does not work on maas deployed machines when rebooting.
I believe this is because of a race with curtin configs.

I have spawned a focal VM on maas and I want to rename the interface.
I create the following config file : 

# cat /etc/netplan/76-awaya.yaml 
network:
  version: 2
  ethernets:
    enp5s0:
      set-name: awaya
      match:
        macaddress: 00:16:3e:e3:a0:bf

When I reboot, the interface does not get renamed :
# reboot
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:16:3e:e3:a0:bf brd ff:ff:ff:ff:ff:ff
    inet6 fd42:568f:86da:6c4a:216:3eff:fee3:a0bf/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 3519sec preferred_lft 3519sec
    inet6 fe80::216:3eff:fee3:a0bf/64 scope link 
       valid_lft forever preferred_lft forever


If I remove the curtin network config file renaming works.

# rm /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg
# reboot 
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: awaya: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:16:3e:e3:a0:bf brd ff:ff:ff:ff:ff:ff
    inet 10.93.227.2/24 brd 10.93.227.255 scope global awaya
       valid_lft forever preferred_lft forever
    inet6 fd42:568f:86da:6c4a:216:3eff:fee3:a0bf/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 3596sec preferred_lft 3596sec
    inet6 fd42:568f:86da:6c4a:0:1::/64 scope global 
       valid_lft forever preferred_lft forever
    inet6 fe80::216:3eff:fee3:a0bf/64 scope link 
       valid_lft forever preferred_lft forever

** Affects: cloud-init
     Importance: Undecided
         Status: Confirmed

** Affects: netplan
     Importance: Undecided
         Status: Confirmed


** Tags: fr-2070

** Also affects: netplan
   Importance: Undecided
       Status: New

** Changed in: cloud-init
       Status: New => Confirmed

** Changed in: netplan
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1961803

Title:
  netplan renaming does not work on maas deployed machines on reboot

Status in cloud-init:
  Confirmed
Status in netplan:
  Confirmed

Bug description:
  Netplan renaming does not work on maas deployed machines when rebooting.
  I believe this is because of a race with curtin configs.

  I have spawned a focal VM on maas and I want to rename the interface.
  I create the following config file : 

  # cat /etc/netplan/76-awaya.yaml 
  network:
    version: 2
    ethernets:
      enp5s0:
        set-name: awaya
        match:
          macaddress: 00:16:3e:e3:a0:bf

  When I reboot, the interface does not get renamed :
  # reboot
  # ip a
  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
         valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host 
         valid_lft forever preferred_lft forever
  2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
      link/ether 00:16:3e:e3:a0:bf brd ff:ff:ff:ff:ff:ff
      inet6 fd42:568f:86da:6c4a:216:3eff:fee3:a0bf/64 scope global dynamic mngtmpaddr noprefixroute 
         valid_lft 3519sec preferred_lft 3519sec
      inet6 fe80::216:3eff:fee3:a0bf/64 scope link 
         valid_lft forever preferred_lft forever

  
  If I remove the curtin network config file renaming works.

  # rm /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg
  # reboot 
  # ip a
  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
         valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host 
         valid_lft forever preferred_lft forever
  2: awaya: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
      link/ether 00:16:3e:e3:a0:bf brd ff:ff:ff:ff:ff:ff
      inet 10.93.227.2/24 brd 10.93.227.255 scope global awaya
         valid_lft forever preferred_lft forever
      inet6 fd42:568f:86da:6c4a:216:3eff:fee3:a0bf/64 scope global dynamic mngtmpaddr noprefixroute 
         valid_lft 3596sec preferred_lft 3596sec
      inet6 fd42:568f:86da:6c4a:0:1::/64 scope global 
         valid_lft forever preferred_lft forever
      inet6 fe80::216:3eff:fee3:a0bf/64 scope link 
         valid_lft forever preferred_lft forever

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1961803/+subscriptions

Follow ups

[Bug 1961803] Re: netplan renaming does not work on maas deployed machines on reboot
From: Lukas Märdian, 2022-02-27
[Bug 1961803] Re: netplan renaming does not work on maas deployed machines on reboot
From: James Falcon, 2022-02-24