Bug 1776927

Summary:	Kickstart default iPXE setting wrong ksdevice when primary interface is not used for provisioning
Product:	Red Hat Satellite	Reporter:	Joniel Pasqualetto <jpasqual>
Component:	Provisioning Templates	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Roman Plevka <rplevka>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	ajambhul, bkearney, mhulan, oprazak
Target Milestone:	6.7.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:27:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joniel Pasqualetto 2019-11-26 15:22:54 UTC

Description of problem:

When host to be provisioned has multiple nics and provision interface is not the primary interface, kernel line generated  for iPXE contains the wrong ksdevice.


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


How reproducible:

always

Steps to Reproduce:
1. Create a host with 2 nics
2. Define one of the nics as primary and the other nic as provisioning
3. Render the iPXE template

Actual results:
mac address of the "ksdevice' parameter is the mac address of the primary  interface.

Expected results:
mac address of the 'ksdevice' parameter should be the mac address of the provision interface.

Additional info:

It's easy to fix, just use the variable @host.provision_interface.mac instead of @host.mac

Comment 3 Ondřej Pražák 2020-02-25 11:08:12 UTC

The change in the iPXE template has made it into 6.7 snaps already. Could QE verify this is fixed?

Comment 4 Roman Plevka 2020-03-05 09:07:42 UTC

VERIFIED
on sat6.7.0-14

The template is updated and correctly set the ksdevice to the MAC address of the provisioning iface

Comment 7 errata-xmlrpc 2020-04-14 13:27:30 UTC

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.

https://access.redhat.com/errata/RHSA-2020:1454