LTSP booting in 18.04 has broken with the recent netplan update; I think due to this patch.
Involved steps:
1) Clients netboot from the LTSP server with something like nfsroot=xxx.
2) Initramfs-tools sets an IP (usually ipv4).
3) LTSP initramfs hooks create an overlay for the file system to make it writable, and create /etc/network/interfaces with the following contents, to prevent the IP from being removed/changed:
auto enp0s3
iface enp0se inet manual
4) Here is the regression, this version of netplan now creates /run/systemd/network/10-netplan-enp0s3.network with these contents:
[Match]
MACAddress=08:00:27:e9:33:39
Name=enp0s3
[Network]
LinkLocalAddressing=ipv6
5) systemd-networkd then sees this configuration and unassigns the interface IP, hanging the clients. I don't know if it was supposed to re-initialize the IP, but it just hangs then.
The workaround we currently use is to remove netplan from the initramfs:
rm /lib/systemd/system-generators/netplan
Could you please tell us of a better way to tell netplan not to assign an IP to the boot interface, or see if it's actually a bug in netplan?
LTSP booting in 18.04 has broken with the recent netplan update; I think due to this patch.
Involved steps:
1) Clients netboot from the LTSP server with something like nfsroot=xxx.
2) Initramfs-tools sets an IP (usually ipv4).
3) LTSP initramfs hooks create an overlay for the file system to make it writable, and create /etc/network/ interfaces with the following contents, to prevent the IP from being removed/changed:
auto enp0s3
iface enp0se inet manual
4) Here is the regression, this version of netplan now creates /run/systemd/ network/ 10-netplan- enp0s3. network with these contents: 08:00:27: e9:33:39
[Match]
MACAddress=
Name=enp0s3
[Network] sing=ipv6
LinkLocalAddres
5) systemd-networkd then sees this configuration and unassigns the interface IP, hanging the clients. I don't know if it was supposed to re-initialize the IP, but it just hangs then.
The workaround we currently use is to remove netplan from the initramfs: system- generators/ netplan
rm /lib/systemd/
Could you please tell us of a better way to tell netplan not to assign an IP to the boot interface, or see if it's actually a bug in netplan?