My latest update in Fedora 21 caused my ethernet connection not to be able to connect, and I can no longer update that system. The network manager version in question is: $ rpm -q NetworkManager NetworkManager-0.9.10.0-10.git20140704.fc21.x86_64 And the log I get follows. The interesting part seems to be "assertion 'priv->client_type != 0' failed", which I have no idea what it means. Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> (eth0): deactivating device (reason 'none') [0] Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Auto-activating connection 'eth0'. Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) starting connection 'eth0' Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> NetworkManager state is now CONNECTING Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0] Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0] Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: client_start: assertion 'priv->client_type != 0' failed Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> (eth0): device state change: ip-config -> failed (reason 'dhcp-start-failed') [70 120 15] Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> NetworkManager state is now DISCONNECTED Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Disabling autoconnect for connection 'eth0'. Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <warn> Activation (eth0) failed for connection 'eth0' Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0] Oct 30 11:43:12 localhost.localdomain NetworkManager[637]: <info> (eth0): deactivating device (reason 'none') [0]
It may be that you don't have any DHCP client installed. $ rpm -q dhclient Please check and update your installation?
$ rpm -q dhclient dhclient-4.3.1-8.fc21.x86_64
I have the same problem with Fedora 21 Beta 4 clean install and also after update. $ rpm -q dhclient dhclient-4.3.1-8.fc21.x86_64
I have the same problem with Fedora 21 Beta 4 clean install and also after update. $ rpm -q dhclient dhclient-4.3.1-8.fc21.x86_64 # systemctl status dhclient ● dhclient.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead)
My issue was solved. creating /etc/dhcp/dhclient.conf and adding the following line solved the issue: send dhcp-client-identifier = hardware; This was found in bug https://bugzilla.redhat.com/show_bug.cgi?id=1154200 DHCP server in this case was a Cisco RV320 Router.
Alexander, thank you for the analysis. *** This bug has been marked as a duplicate of bug 1154200 ***