Created attachment 1414776 [details]
rpm -qa after upgrade

Description of problem:
When I upgrade F27 Workstation or F26 Workstation to F28 Workstation, the wired connection is disabled on boot. This happens in a VM (libvirt, kvm), but we haven't reproduced it on bare metal. In VM though, we reproduced this on two different hosts, so it's not a fluke.

The problem can be resolved by connecting to wired network in GNOME menus or by running:
$ nmcli device connect enp0s3
Once that is done, it auto-connects even on following reboots.

Version-Release number of selected component (if applicable):
NetworkManager-1.10.4-1.fc28.x86_64

How reproducible:
always

Steps to Reproduce:
1. install F27 Workstation from netinst (i.e. fully updated)
2. upgrade to F28 using dnf system-upgrade
3. after F28 boots, notice that network connections don't work, and default device enp0s3 is disconnected. This persists after reboots.
4. Connect using nmcli, the network then works even after reboots.

Actual results:
network doesn't work after upgrade

Expected results:
network works after upgrade

Additional info:
After upgrade, this is the state:

$ 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
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:a7:c9:9a brd ff:ff:ff:ff:ff:ff
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:33:e5:84 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:33:e5:84 brd ff:ff:ff:ff:ff:ff

$ nmcli device status
DEVICE      TYPE      STATE         CONNECTION 
virbr0      bridge    connected     virbr0     
enp0s3      ethernet  disconnected  --         
lo          loopback  unmanaged     --         
virbr0-nic  tun       unmanaged     --         


After connecting it, it looks like this:

$ nmcli device connect enp0s3 
Device 'enp0s3' successfully activated with 'b26e5a75-203e-4e41-bcff-315f67af1e8f'.

$ nmcli device status
DEVICE      TYPE      STATE      CONNECTION 
enp0s3      ethernet  connected  enp0s3     
virbr0      bridge    connected  virbr0     
lo          loopback  unmanaged  --         
virbr0-nic  tun       unmanaged  --         

$ 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
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 52:54:00:a7:c9:9a brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.49/24 brd 192.168.11.255 scope global dynamic noprefixroute enp0s3
       valid_lft 3475sec preferred_lft 3475sec
    inet6 fe80::7e7a:bda:3708:2368/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:33:e5:84 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:33:e5:84 brd ff:ff:ff:ff:ff:ff