Bug 1956494 - kickstart_kernel_options doesn't handle properly tagged vlan over bond device
Summary: kickstart_kernel_options doesn't handle properly tagged vlan over bond device
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-03 19:14 UTC by Joniel Pasqualetto
Modified: 2021-05-10 14:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32497 0 Normal New kickstart_kernel_options doesn't handle properly tagged vlan over bond device 2021-05-03 19:19:33 UTC
Github theforeman foreman pull 8493 0 None open Fixes #32497 - allow template to properly manage vlan tag over bond interface 2021-05-03 19:30:21 UTC

Description Joniel Pasqualetto 2021-05-03 19:14:59 UTC
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:


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