Created attachment 977586 [details] system log for failed network connection Description of problem: After yesterdays's update of NetworkManager suite (0.9.10.1-1.git20150105.fc21) NetworkManager fails to reliably setup a standard DHCP IPv4 connection on a wired Ethernet interface. The PC has 1 wired Ethernet on-board interface. No WLAN, no other network-capable interfaces. Based on defaults after standard F21 installation. NetworkManager is configured to automatically setup the interface on boot-time. Pretty basic setup. On boot-time, NetworkManager usually works fine up to successfully getting all network details from DHCP server (IP address, mask, domain, nameserver, etc) but then fails at end of so-called "Phase 4" (of 5) and removes the assigned IP address. After boot, repeated calls of "systemctl restart NetworkManager" (command line) eventually succeed and make the network work. In about 8 of 10 calls, NetworkManager gets stuck and "nmcli g" shows network either as "disconnected" or "connecting" (but not connected). However, "ifoncig" (or "ip addr") already shows an IP address on the interface (so network is technically working, but NetworkManager stack returns failure to all programs asking for network state, eg, Firefox, Thunderbird). In about 2 of 10 calls, NetworkManager works as it should (and did before the recent update). Version-Release number of selected component (if applicable): 0.9.10.1-1.git20150105.fc21 (last working version: 0.9.10.0-14.git20140704.fc21) How reproducible: "Unfortunately", NetworkManager doesn't fail always but just most of the time. Steps to Reproduce: 1. systemctl restart NetworkManager 2. nmcli g 3. ifconfig (or "ip addr") Actual results: In most cases, "nmcli g" shows either... STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN disconnected none enabled enabled enabled enabled ...or... STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connecting none enabled enabled enabled enabled Although "ifconfig" (or "ip addr") clearly shows proper IPv4 configuration. Technically, network works but NetworkManager thinks something is missing. Expected results: "nmcli g" should always show... STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled enabled Additional info: Update of NetworkManager packages didn't change anything in /etc/dhcp, /etc/NetworkManager or /etc/sysconfig/network-scripts. So configuration hasn't changed. Currently, there's no known work-around. Only solution is to repeatedly run "systemctl restart NetworkManager" until "nmcli g" shows "connected".
Created attachment 977587 [details] system log for successful network setup This is how it should look like to setup DHCP network setup. NetworkManager doesn't get stuck after end of Phase 4 but continues with Phase 5 (of 5).
After the update, NM fails to set up both mobile broadband and WiFi connections on my laptop. Both seem to time out on DHCP. So this problem does not seem to be limited to wired connections. It's also not unpredictable on my system: I haven't got it to work once with either mobile broadband or WiFi since the update, despite trying numerous times. USB tethering to my Android phone works.
I just downgraded NetworkManager using yum from 0.9.10.1-1.git20150105 to 0.9.10.0-13.git20140704 (all NetworkManager* packages) and now both mobile broadband and WiFi connections work again. (This episode was not a nice surprise, excluding NetworkManager from updates.)
*** This bug has been marked as a duplicate of bug 1181477 ***