Bug 588815

Summary:	NetworkManager-0.8.0-11.git20100503.fc13 no longer brings up "Auto eth1" network
Product:	[Fedora] Fedora	Reporter:	Orion Poplawski <orion>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	13	CC:	dcbw
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-05-04 21:39:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Orion Poplawski 2010-05-04 16:45:53 UTC

Description of problem:

Rebooted after installing today's updates-testing updates including NetworkManager-0.8.0-11.git20100503.fc13.i686, dhclient-4.1.1-21.fc13.i686, kernel-PAE-2.6.33.3-72.fc13 and now my network will no longer come up.   Log from attempt to connect:

May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) starting connection 'Auto eth1'
May  4 08:37:41 orca NetworkManager: <info> (eth1): device state change: 3 -> 4 (reason 0)
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled...
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete.
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting...
May  4 08:37:41 orca NetworkManager: <info> (eth1): device state change: 4 -> 5 (reason 0)
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) successful.
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete.
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started...
May  4 08:37:41 orca NetworkManager: <info> (eth1): device state change: 5 -> 7 (reason 0)
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Beginning DHCPv4 transaction (timeout in 45 seconds)
May  4 08:37:41 orca NetworkManager: <info> dhclient started with pid 2421
May  4 08:37:41 orca NetworkManager: <info> (eth1): device state change: 7 -> 9 (reason 0)
May  4 08:37:41 orca NetworkManager: <info> Marking connection 'Auto eth1' invalid.
May  4 08:37:41 orca NetworkManager: <warn> Activation (eth1) failed.
May  4 08:37:41 orca NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
May  4 08:37:41 orca NetworkManager: <info> (eth1): device state change: 9 -> 3 (reason 0)
May  4 08:37:41 orca NetworkManager: <info> (eth1): deactivating device (reason: 0).
May  4 08:37:41 orca NetworkManager: <info> (eth1): canceled DHCP transaction, DHCP client pid 2421

This connection is a Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet card that I added to the machine.  There was no ifcfg-eth1 for it and was working fine for a couple days.

I created an ifcfg-eth1 and used ifup eth1 to bring up the network.  With ifcfg-eth1 present, NM is able to activate the network.

Downgraded dhclient but same behavior.

Downgraded NM and it is now able to activate "Auto eth1" automatically again.

Comment 1 Dan Williams 2010-05-04 21:39:34 UTC


*** This bug has been marked as a duplicate of bug 588814 ***