Description of problem:
--activate and --onboot options are not honored when configuring bridge devices in kickstart
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Run installation (eg in kvm with 2 network devices) with ip=ens3:dhcp network boot option and the kickstart network configuration:
network --device=bridge0 --bridgeslaves=ens3 --bootproto=dhcp --onboot=no
network --device=bridge1 --bridgeslaves=ens4 --bootproto=dhcp
bridge1 is activated in installer
slave of bridge0 has ONBOOT=yes set in ifcfg file (ifcfg-bridge0_slave1)
bridge1 is not activated in installer (because no --activate option is set)
slave of bridge0 has ONBOOT=no set in ifcfg file (ifcfg-bridge0_slave1)
for bug 1416655.
Verified on RHEL-7.4-20170504.0 with anaconda-22.214.171.124-1.el7. Thanks.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.