Description of problem:

--activate and --onboot options are not honored when configuring bridge devices in included kickstart snippet created in %pre section:

(only ens3 device is activated in dracut via boot option ip=ens3:dhcp)

%include /tmp/ksinclude
%pre
echo "network --device=bridge0  --bridgeslaves=ens3 --bootproto=dhcp --onboot=no" >> /tmp/ksinclude
echo "network --device=bridge1  --bridgeslaves=ens4 --bootproto=dhcp" >> /tmp/ksinclude
%end

We shoud also unify the names of ifcfg files for bridge slaves with non-%pre kickstart case,
ie instead of overwriting ifcfg-ens3, write additional ifcfg-bridge0_slave1


Version-Release number of selected component (if applicable):

RHEL 7.3
anaconda-21.48.22.93-1

How reproducible:


Steps to Reproduce:

Run installation (eg in kvm with 2 network devices) with ip=ens3:dhcp network boot option and the kickstart network configuration
%include /tmp/ksinclude
%pre
echo "network --device=bridge0  --bridgeslaves=ens3 --bootproto=dhcp --onboot=no" >> /tmp/ksinclude
echo "network --device=bridge1  --bridgeslaves=ens4 --bootproto=dhcp" >> /tmp/ksinclude
%end


Actual results:

bridge0 is not activated in installer
bridge1 is activated in installer
bridge0 has ONBOOT=no
slave of bridge0 (ifcfg-ens3) has ONBOOT=yes
bridge1 has ONBOOT=yes
slave of bridge1 (ifcfg-ens4) has ONBOOT=yes


Expected results:

The first network command has --activate set by default, so the expected results are:

bridge0 is activated in installer
bridge1 is not activated in installer
bridge0 has ONBOOT=no
slave of bridge0 (ifcfg-bridge0_slave1) has ONBOOT=no
bridge1 has ONBOOT=yes
slave of bridge1 (ifcfg-bridge1_slave1) has ONBOOT=yes

Additional info:

I'll add link to our kickstart test for this case.