Bug 729085

Summary: Is initscripts meant to assume NetworkManager is installed?
Product: [Fedora] Fedora Reporter: Göran Uddeborg <goeran>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: iarlyy, jonathan, notting, plautrba, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-08 17:52:34 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:

Description Göran Uddeborg 2011-08-08 17:12:09 UTC 
While digging into a boot problem, I discovered something that looks a bit odd to me:

The initscripts package does not require (as per RPM) the NetworkManager package.  On my machines "rpm --test -e NetworkManager" doesn't complain, it says it would be ok to remove it.

At the same time, there is nothing in the scripts in initscripts that checks if the nmcli command  is available.  The scripts just runs it, obviously assuming nmcli to be there.

To me it would seem better if either
- the scripts checked if nmcli is available before trying to use it, or
- the initscripts package did require the NetworkManager package or the /usr/bi/nmcli file.

One COULD argue that it is correct as it is, and assuming administrators to know they have to set NM_CONTROLLED to no in all ifcfg files if they choose not to install NetworkManager.  This requirement is not very obvious to the administrator (a.k.a. me :-), though.
Comment 1 Bill Nottingham 2011-08-08 17:34:33 UTC 
It's fallthrough - if nmcli is not installed, the right thing should happen.
Comment 2 Göran Uddeborg 2011-08-08 17:52:34 UTC 
Ok, then I guess it is ok as it is.