Public bug reported:
Consider the example below:
network:
renderer: NetworkManager
ethernets:
eth0: {}
eth1: {}
renderer: networkd
bonds:
bond0: {}
bond1: {}
renderer: networkd
It's expected that networkd would be used for ethernets and bonds but
it's actually lost:
$ netplan get --root-dir /tmp/fakeroot
network:
version: 2
renderer: NetworkManager
ethernets:
eth0: {}
eth1: {}
bonds:
bond0: {}
bond1: {}
In this case all the configuration will be generated for Network
Manager.
When it's moved to the top it is set per netdef:
$ cat /tmp/fakeroot/etc/netplan/asd.yaml
network:
renderer: NetworkManager
ethernets:
renderer: networkd
eth0: {}
eth1: {}
bonds:
renderer: networkd
bond0: {}
bond1: {}
$ netplan get --root-dir /tmp/fakeroot
network:
version: 2
renderer: NetworkManager
ethernets:
eth0:
renderer: networkd
eth1:
renderer: networkd
bonds:
bond0:
renderer: networkd
bond1:
renderer: networkd
** Affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2077636
Title:
renderer property lost when set at the end of a network.<type> stanza
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2077636/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
