Bug 1956494

Description of problem:

When a host to be provisioned has a virtual interface that requires a VLAN tag and is attached to a bond device, the kernel options simply ignore the bond device, creating only the VLAN. Therefore, dracut does not get configured properly and provisioning fails.

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


How reproducible:


Steps to Reproduce:
1. Create a new host
2. Add 2 physical interfaces and mark both only as "managed"
3. Add a bond device using the 2 physical interfaces. Mark only the option "managed" to this interface too
4. Create a virtual interface, set a vlan tag and put the bond a master interface
5. Look at the rendered template "PXEGrub template" for example. You'll see something like this (pasting only the part of the line that 

~~~
(...)

... network ksdevice=bootif ks.device=bootif kssendmac ks.sendmac inst.ks.sendmac ip=192.168.250.81::192.168.250.1:255.255.255.0:ryan-blacher.example.local:vlan409:none nameserver=192.168.250.100 vlan=vlan409:bond0
~~~

Note that the vlan is defined and it points to the device "bond0", but the bond device is not configured.

Actual results:

Rendered template looks like this:

~~~
(...)

... network ksdevice=bootif ks.device=bootif kssendmac ks.sendmac inst.ks.sendmac ip=192.168.250.81::192.168.250.1:255.255.255.0:ryan-blacher.example.local:vlan409:none nameserver=192.168.250.100 vlan=vlan409:bond0
~~~

Expected results:

~~~
(...)
... network ksdevice=bootif ks.device=bootif kssendmac ks.sendmac inst.ks.sendmac ip=192.168.250.81::192.168.250.1:255.255.255.0:ryan-blacher.example.local:vlan409:none nameserver=192.168.250.100 bond=bond0:eth0,eth1:mode=active-backup,miimon=200 vlan=vlan409:bond0
~~~

Additional info: