Bug 708908

Summary: Wired Network does not become active during boot up after update to NetworkManager 0.8.999-3.git20110526.fc15
Product: [Fedora] Fedora Reporter: John T. Folden <john.t.folden>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: dcbw, jklimes
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-03 08:19:33 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:
Attachments:
Description Flags
/var/log/messages none

Description John T. Folden 2011-05-30 05:46:13 UTC 
Description of problem:
Prior to updating, system was configured to make the default wired network connection available to all users and would become active during bootup. After the update, the network does not connect until after a user logs into his account.

Version-Release number of selected component (if applicable):
0.8.999-3.git20110526.fc15

How reproducible:
100% of the time

Steps to Reproduce:
1. Install Update
2. restart system
3. System is unreachable on network until a user logs in.
  
Actual results:
Network is not active until a user logs in

Expected results:
Network connection should become active during bootup

Additional info:
Downgrading NetworkManager, NetworkManager-glib and NetworkManager-gnome to prior release and restarting results in expected behavior.
Comment 1 Jirka Klimes 2011-05-30 20:18:52 UTC 
Do you see a NM crash? It could be duplicate of #708445
Comment 2 John T. Folden 2011-05-30 22:18:12 UTC 
No, I skimmed over the log from yesterday and there were no readily apparent crashes that I could see.
Comment 3 Jirka Klimes 2011-05-31 11:55:56 UTC 
Could you provide the following info?

1. nmcli -f all con list
2. /var/log/messages file
Comment 4 John T. Folden 2011-06-03 06:50:18 UTC 
Created attachment 502736 [details]
/var/log/messages
Comment 5 John T. Folden 2011-06-03 06:51:01 UTC 
Hi,

hopefully this plus the attachment is what you need.


$ nmcli -f all con list
NAME                      UUID                                   TYPE              TIMESTAMP    TIMESTAMP-REAL                     AUTOCONNECT   READONLY   DBUS-PATH                                 
System em1                1dad842d-1912-ef5a-a43a-bc238fb267e7   802-3-ethernet    1307083448   Fri 03 Jun 2011 02:44:08 AM EDT    yes           no         /org/freedesktop/NetworkManager/Settings/0
Comment 6 Jirka Klimes 2011-06-03 08:19:33 UTC 
The log in the comment #4 shows the same crash as in bug 708445.
Please upgrade NetworkManager and you should be fine.

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