Bug 708677 - Network manager is not working anymore
Summary: Network manager is not working anymore
Keywords:
Status: CLOSED DUPLICATE of bug 708445
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 15
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-28 19:31 UTC by Franco Violi
Modified: 2011-05-30 20:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-30 20:11:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
The /var/log/message of interest (22.22 KB, text/plain)
2011-05-28 19:36 UTC, Franco Violi
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.