I have found another case where reloading networkd will not be enough to
apply the configuration. I'm not sure if it's the same root cause but it
looks similar so I'll use this ticket to document it.
The scenario looks like this (it's all done in a LXD VM running
Oracular):
1) Start with the default ethernet configuration
2) Add the ethernet interface to a bond and apply
3) Remove the bond from the configuration and apply
4) Add the interface back to the bond and apply
5) At this point the configuration will not be applied anymore and one needs to
either restart networkd or delete the bond.
It smells like some state is not being dropped and causing the issue.
Details on how to reproduce:
Start with this config:
network:
version: 2
ethernets:
enp5s0:
dhcp4: true
Add a bond:
network:
version: 2
ethernets:
enp5s0: {}
bonds:
bond0:
dhcp4: true
interfaces:
- enp5s0
Apply the config and observe it worked as intended.
Now restore the initial config and netplan apply again:
network:
version: 2
ethernets:
enp5s0:
dhcp4: true
At this point enp4s0 will get an IP address and the bond0 interface will
be left behind as netplan apply will not delete it.
Now add the bond back and netplan apply again:
network:
version: 2
ethernets:
enp5s0: {}
bonds:
bond0:
dhcp4: true
interfaces:
- enp5s0
At this point the configuration will not by applied anymore.
The bond state will get stuck at "State: no-carrier (configuring)".
One needs to either delete the bond or restart networkd to make it work again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058976
Title:
Configuration files for networkd are created when NetworkManager is
the default renderer
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2058976/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
