Bug 441679

Summary: Choosing not to install NetworkManager leaves system without networking on bootup
Product: [Fedora] Fedora Reporter: Charles R. Anderson <cra>
Component: distributionAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Bill Nottingham <notting>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: dcantrell, dcbw, katzj, k.georgiou, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-17 15:37:18 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 235706    

Description Charles R. Anderson 2008-04-09 09:53:28 EDT
Description of problem:

Deselecting NetworkManager in anaconda leaves the installed system without any
way to start the network automatically on first bootup.  Can we please enable
the "network" service in this case?
Comment 1 Jesse Keating 2008-04-09 10:05:05 EDT
Hrm, I don't know if we want to handle that.  Perhaps we should just make
NetworkManager a required rather than a default or optional.
Comment 2 Jeremy Katz 2008-04-09 10:06:27 EDT
Doing things like this doesn't scale.  Fix the packages, either by having
initscripts require NetworkManager or marking the package required rather than
default in comps.

Reassigning to distribution to duke that out there :)
Comment 3 Bill Nottingham 2008-04-17 15:37:18 EDT
Fixed in comps to be mandatory for the 'Base' group.