Bug 1279672 - If parse-kickstart configures a bonded network device and NetworkManager is uninstalled or disabled the bonded device does not work
If parse-kickstart configures a bonded network device and NetworkManager is u...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda (Show other bugs)
7.1
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Anaconda Maintenance Team
Release Test Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-09 21:16 EST by Derek Schrock
Modified: 2015-11-10 08:41 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-10 08:41:48 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Derek Schrock 2015-11-09 21:16:51 EST
Description of problem:
If you configure a bonded network device that is parsed by anaconda parse-kickstart and NetworkManager is uninstalled (%post or after reboot) or disabled the bonded device does not work.


How reproducible:
1) Kickstart a machine with network lines such that parse-kickstart reads
2) Uninstall NetworkManager or disable NetworkManager
3) restart
4) bonded network device does not work.

Reinstalling/reenabling NetworkingManager and a reboot will bring the bonded network device back.


Actual results:
bonding device no longer works if NetworkManager uninstalled or disabled after reboot 

Expected results:

bonded device to continue to work no matter the state (running/uninstalled/disabled) of NetworkManager.
Comment 2 Chris Lumens 2015-11-10 08:41:48 EST
NetworkManager is what we use for network configuration in RHEL7.  If you uninstall NetworkManager, it is entirely likely that network stuff will break, yes.  However it is then incumbent upon you to do the network configuration yourself.  We aren't going to ship code to configure networks two different ways - we've already got one that works.  Sorry.

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