Bug 708677

Summary: Network manager is not working anymore
Product: [Fedora] Fedora Reporter: Franco Violi <franco.violi>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 15CC: bloch, dcbw, djuran, gilboad, jklimes, uraeus
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-05-30 20:11:42 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
The /var/log/message of interest none

Description Franco Violi 2011-05-28 19:31:38 UTC 
Description of problem:


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


How reproducible:install the update


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: After installing the update, the network manager is no more working. I add to manage the interfaces via command line to get back on line.
In attachement the system log of the problem.
Comment 1 Franco Violi 2011-05-28 19:36:46 UTC 
Created attachment 501518 [details]
The /var/log/message of interest

The var log messages
Comment 2 Gilboa Davara 2011-05-29 08:35:27 UTC 
I can confirm the above.
Since the git20110526 update, NM is eating 100% CPU and locked in the following loop:
[41277.281190] NetworkManager[12755]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-Auto_InsecureNetwork
....
[41278.046820] NetworkManager[12755]: ifcfg-rh: updating /etc/sysconfig/network-scripts/ifcfg-Auto_InsecureNetwork

- Gilboa
Comment 3 Gilboa Davara 2011-05-29 08:38:13 UTC 
This bug is most likely a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=708626.

- Gilboa
Comment 4 Christian Schaller 2011-05-30 09:29:17 UTC 
I also got this bug after latest yum upgrade, this is also most likely a duplicate of bug 708445
Comment 5 Jirka Klimes 2011-05-30 20:11:42 UTC 

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