[SOLVED] Static network assignement breaks after updating systemd in Fedora container

[gankarloo]

I'm using the standard fedora lxc Fedora 31 container.
Everything works great until I update the system.

After running dnf update in the container the ip assignement stops working after reboot.

pveversion
pve-manager/6.1-8/806edfe1 (running kernel: 5.3.18-2-pve)

systemd version on a working container

[root@fedora31-2 ~]# rpm -qa |grep systemd
systemd-udev-243-4.gitef67743.fc31.x86_64
systemd-rpm-macros-243-4.gitef67743.fc31.noarch
systemd-libs-243-4.gitef67743.fc31.x86_64
systemd-pam-243-4.gitef67743.fc31.x86_64
systemd-bootchart-233-5.fc31.x86_64
systemd-243-4.gitef67743.fc31.x86_64

systemd version after upgrade NOT working

[root@feddan5 ~]# rpm -qa|grep systemd
systemd-udev-243.7-1.fc31.x86_64
systemd-rpm-macros-243.7-1.fc31.noarch
systemd-libs-243.7-1.fc31.x86_64
systemd-pam-243.7-1.fc31.x86_64
systemd-bootchart-233-5.fc31.x86_64
systemd-243.7-1.fc31.x86_64

I'm attaching logs from both a working container and one thats not working
with DEBUG enabled for systemd-networkd

Here is a full listing of pveversion -v

proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-8 (running version: 6.1-8/806edfe1)
pve-kernel-helper: 6.1-7
pve-kernel-5.3: 6.1-5
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-4.15.18-26-pve: 4.15.18-54
pve-kernel-4.4.134-1-pve: 4.4.134-112
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-17
libpve-guest-common-perl: 3.0-5
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 3.0.3-pve60
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-3
pve-cluster: 6.1-4
pve-container: 3.0-22
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.0-10
pve-firmware: 3.0-6
pve-ha-manager: 3.0-9
pve-i18n: 2.0-4
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-7
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

container config working

root@pve-3:~# cat /etc/pve/lxc/129.conf
arch: amd64
cores: 1
hostname: fedora31-2
memory: 512
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.1.1,hwaddr=66:DF:66:0B:01:C1,ip=192.168.1.41/24,type=veth
ostype: fedora
rootfs: local-zfs:subvol-129-disk-0,size=8G
swap: 512
unprivileged: 1

container config NOT working

root@pve-3:~# cat /etc/pve/lxc/130.conf
arch: amd64
cores: 1
hostname: feddan5
memory: 512
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.1.1,hwaddr=A6:2F:8D:C9:24:9C,ip=192.168.1.42/24,type=veth
ostype: fedora
rootfs: local-zfs:subvol-130-disk-0,size=8G
swap: 512
unprivileged: 1

 

[Stoiko Ivanov]

This could be related to recent changes in systemd - see the following thread https://forum.proxmox.com/threads/systemd-244-1-breaks-networking-in-lxc.61862/#post-301545

and the discussion on the pve-devel mailing list:
https://pve.proxmox.com/pipermail/pve-devel/2020-March/042424.html

I hope this helps!

 

[gankarloo]

Solved by the info in https://forum.proxmox.com/threads/systemd-244-1-breaks-networking-in-lxc.61862/#post-301545