Fedora 31 CT looses network connectivity after dfm update and reboot

Feb 29, 2020
5
0
1
44
I've installed a container using fedora-31-default_20191029_amd64.tar.xz on Proxmox Virtual Environment 6.1-7


After I've installed the container with the above template and do a dfm update then reboot, I loose network connectivity. Here's an example...

Code:
vm-test-106 login: root
Password:
Last failed login: Sun Mar 15 15:01:17 UTC 2020 on tty1
[root@vm-test-106 ~]# ip a
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
95: eth0@if96: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 82:d9:81:71:47:a7 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 192.168.14.119/24 brd 192.168.14.255 scope global dynamic eth0
       valid_lft 7189sec preferred_lft 7189sec
    inet6 fe80::80d9:81ff:fe71:47a7/64 scope link
       valid_lft forever preferred_lft forever
[root@vm-test-106 ~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=15.5 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 15.486/15.486/15.486/0.000 ms

--- reboot ---

vm-test-106 login: root
Password:
Last login: Sun Mar 15 15:01:20 on tty1
[root@vm-test-106 ~]# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=10.7 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=12.0 ms

--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 10.694/11.367/12.040/0.673 ms


(performs dnf update and reboot)


vm-test-106 login: root
Password:
Last login: Sun Mar 15 15:02:02 on tty1
[root@vm-test-106 ~]# ip a
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
105: eth0@if106: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 82:d9:81:71:47:a7 brd ff:ff:ff:ff:ff:ff link-netnsid 0
[root@vm-test-106 ~]#
If I update the network settings from within proxmox, the VM will update and work, however upon reboot it goes back to the above behavior.

Am I doing something wrong here? I'm relatively inexperienced with Proxmox but for the most part my experience has been rather straight forward.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!