Bug 459120

Summary: NM_CONTROLED default value
Product: [Fedora] Fedora Reporter: Jiri Moskovcak <jmoskovc>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: dcbw, dfediuck, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-08-14 18:10:57 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:
Bug Depends On:    
Bug Blocks: 438902    

Description Jiri Moskovcak 2008-08-14 15:03:15 UTC
Description of problem:
NetworkManager takes control over device even if NM_CONTROLED= is not set. The default value for other settings in ifcfg-* scripts is 'no' so it should be the same for NM.

Comment 1 Dan Williams 2008-08-14 18:10:57 UTC
This is by design.  NM will only treat a device as unmanaged if NM_CONTROLLED=no is specified in the ifcfg.  What's the real problem here?  The defaults don't need to be consistent (and some aren't, like PEERDNS defaults to yes).

Comment 2 Jiri Moskovcak 2008-08-15 08:51:53 UTC
The problem is if someone creates ifcfg-* file by hand without any mention of NM he can be confused why NM is taking control over the card. So I think better solution would be to make anaconda to write NM_CONTROLLED=yes into config files and make deafult 'no'.

Jirka