Verification-done on bionic with netplan.io 0.40.1~18.04.2:
Using the following config:
network:
version: 2
ethernets:
maas0:
addresses:
- 10.3.21.29/20
gateway4: 10.3.16.1
match:
macaddress: 52:54:00:4d:3e:84
mtu: 1500
set-name: maas0
The interface renaming is correctly done at boot time; then changing
set-name to 'maas1', bringing down the interface with 'ip link set dev
maas0 down', and running 'netplan apply'; the interface is correctly
renamed:
ubuntu@nice-baboon:~$ sudo vi /etc/netplan/50-cloud-init.yaml
ubuntu@nice-baboon:~$ sudo netplan apply
ubuntu@nice-baboon:~$ ip addr
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: maas0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether 52:54:00:4d:3e:84 brd ff:ff:ff:ff:ff:ff
inet 10.3.21.29/20 brd 10.3.31.255 scope global maas0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe4d:3e84/64 scope link
valid_lft forever preferred_lft forever
ubuntu@nice-baboon:~$
ubuntu@nice-baboon:~$ sudo vi /etc/netplan/50-cloud-init.yaml
ubuntu@nice-baboon:~$ ip link set dev maas0 down
RTNETLINK answers: Operation not permitted
ubuntu@nice-baboon:~$ sudo !!
sudo ip link set dev maas0 down
ubuntu@nice-baboon:~$ ip addr
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: maas0: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group
default qlen 1000
link/ether 52:54:00:4d:3e:84 brd ff:ff:ff:ff:ff:ff
inet 10.3.21.29/20 brd 10.3.31.255 scope global maas0
valid_lft forever preferred_lft forever
ubuntu@nice-baboon:~$ sudo netplan apply
ubuntu@nice-baboon:~$ ip addr
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: maas1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether 52:54:00:4d:3e:84 brd ff:ff:ff:ff:ff:ff
inet 10.3.21.29/20 brd 10.3.31.255 scope global maas1
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe4d:3e84/64 scope link
valid_lft forever preferred_lft forever
** Tags removed: verification-failed-bionic verification-needed
** Tags added: verification-done-bionic
** Tags removed: verification-done-xenial verification-needed-cosmic
** Tags added: verification-needed-xenial
** Tags removed: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770082
Title:
systemd-networkd not renaming devices on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
