Hide Forgot
Description of problem: NetworkManager stopped eth0 despite NM_CONTROLLED=no in /etc/sysconfig/network-scripts/ifcfg-eth0 Version-Release number of selected component (if applicable): NetworkManager-0.7.0.99-3.fc9.i386 Expected results: NetworkManager should respect the directive not to control eth0 Additional info: I only have NetworkManager because it is a dependency for evolution. I don't want it and it is normally turned off. The March upgrade to NetworkManager-0.7.0.99-3.fc9.i386 turned on the service without my noticing (I am 4000 miles from the machine) and when I restarted Fedora two days ago networking first came on as it should, but then NetworkManager started and killed eth0 again. I had to get someone to go to my office and fix it. NetworkManger should not have touched eth0: /etc/sysconfig/network-scripts/ifcfg-eth0 has "NM_CONTROLLED=no" (In addition the package update should not have changed the status of the service -- I have filed a separate bug for this)
Reporter, could you please attach your /var/log/messages while NM changed the status of eth0. Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 338608 [details] messages from boot to soon after NetworkManager disables eth0
Reporter, can you please update to NetworkManager-0.7.0.100-1.fc9 and attach your /etc/sysconfig/network-scripts/ifcfg-eth0 file? Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 339006 [details] ifcfg-eth0 as requested You asked me also to update to NetworkManager-0.7.0.100-1.fc9. Can you give a link for this? It does not seem to be yet on fedora-updates or fedora-updates-testing.
Thank you for reporting this bug. This bug report might be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=457098 -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I don't think it is a duplicate. Bug 457098 refers to behaviour on changing status of the service from on to off. In my case service came on (unintentionally) and was not turned off. But both seem to refer to NetworkManager touching an interface that it had been told not to touch, so maybe it is a duplicate.
Found and fixed upstream: 10bf56b0d6db7281505ca020d1a35ab943dd6b62 (0.7) e5146b8f82bfb68bcdf43f99dddbfaec516a37a3 (head) Was going to tag and release 0.7.1 today, and you seem to have found the last bug before release :) Thanks for helping make the release better.
NetworkManager-0.7.1-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/NetworkManager-0.7.1-1.fc10
NetworkManager-0.7.1-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/NetworkManager-0.7.1-1.fc9
NetworkManager-0.7.1-1.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update NetworkManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-3686
Tested on a laptop with fc10 and bug seems to be fixed. I won't test on the machine where the bug first hit me, since I can't rescue it if a network problem does occur (I'm 4000 miles away), but I'm pretty confident there would be no problem.
NetworkManager-0.7.1-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
NetworkManager-0.7.1-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.