Bug 1071592

Summary: Wired device no longer configurable after update to 0.9.9.0-31.git20131003
Product: [Fedora] Fedora Reporter: Vallimar <vallimar>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-05 22:30:37 UTC Type: Bug
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
Screenshot with working NM version
none
This is how it looks with the non-working NM version none

Description Vallimar 2014-03-02 03:43:38 UTC 
Created attachment 869536 [details]
Screenshot with working NM version

Description of problem:
My wired device is no longer displayed under network settings in the control panel after updating.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.0-31.git20131003.fc20.x86_64

How reproducible:
Everytime I pull up Network Settings.

Steps to Reproduce:
1. Open gnome-control-center
2. Open Network

Actual results:
Only Network Proxy settings are displayed

Expected results:
My wired device should also be displayed

Additional info:
Downgrading to NetworkManager-0.9.9.0-20.git20131003.fc20.x86_64 restores the lost functionality.
Comment 1 Vallimar 2014-03-02 03:44:30 UTC 
Created attachment 869537 [details]
This is how it looks with the non-working NM version
Comment 2 Vallimar 2014-03-04 13:43:29 UTC 
I played with more versions, and the break occurs when going from 0.9.9.0-30 to 0.9.9.0-31. The problem can be seen via nmcli also, the -31 version lists no devices at all, not even loopback. Under -30, my loopbak and ethernet device are shown as expected.
Comment 3 Vallimar 2014-03-05 22:30:37 UTC 
Had some time so I made some worst-case preparations and did a reboot with the update even though it looked highly suspicious as to whether or not it would work and it seems to function normally after the reboot. Just raised all sorts of alarms with me by acting so funky after the update that I was hesitant to risk it after getting burned on supposedly good updates in the past.