Bug 1950929

Summary:	Cannot build a RHEL 8.3 system via Satellite Discovery kexec
Product:	Red Hat Satellite	Reporter:	Lukas Zapletal <lzap>
Component:	Discovery Plugin	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED ERRATA	QA Contact:	Roman Plevka <rplevka>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	bbuckingham, ben.formosa, egolov, hartsjc, jjeffers, jpasqual, lzap, rabajaj, saydas
Target Milestone:	6.9.3	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_discovery-16.3.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1966626 (view as bug list)		Environment:
Last Closed:	2021-07-01 14:56:48 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 Lukas Zapletal 2021-04-19 08:03:41 UTC

RHEL 8.3 no longer accepts 00- in BOOTIF kernel command line argument and therefore the correct interface is not picked. We have fixed bootdisk workflows however missed the discovery kexec workflow:

https://bugzilla.redhat.com/show_bug.cgi?id=1919400

This BZ will track a simple template change for discovery workflow. Since this is a regression, I propose z-streams.

Comment 1 Bryan Kearney 2021-04-22 20:05:03 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32341 has been resolved.

Comment 2 Lukas Zapletal 2021-04-27 09:17:47 UTC

Please rebase to foreman_discovery-16.3.5

https://github.com/theforeman/foreman-packaging/pull/6563

Comment 7 Roman Plevka 2021-06-15 12:26:23 UTC

I'm seeing the following in the kernel args during kexec-ing:

ksdevice=bootif BOOTIF=0156-6f-0d-72-0a-9d

Is the missing delimmiting dash between first two bytes intended?

My host is unable to fetch the kickstart from the server so I'm trying to understand whether this is the issue or it's just my env being configured incorrectly.

Comment 8 Roman Plevka 2021-06-15 12:49:33 UTC

FAILED QA
so this really looks likean issue with the patch -

I submitted another patch to fix the missing delimiting dash:
https://github.com/theforeman/foreman_discovery/pull/542

Comment 9 Lukas Zapletal 2021-06-16 05:56:18 UTC

It is indeed an issue, overlook in the template:

https://github.com/theforeman/foreman_discovery/pull/543

Comment 10 Lukas Zapletal 2021-06-16 07:55:04 UTC

Please rebase to 16.3.6 which I pushed to rubygems.org. I am not doing any upstream release as 2.3 is no longer supported. Doing 2.5 instead.

Comment 11 Evgeni Golov 2021-06-16 09:17:23 UTC

(In reply to Lukas Zapletal from comment #10)
> Please rebase to 16.3.6 which I pushed to rubygems.org. I am not doing any
> upstream release as 2.3 is no longer supported. Doing 2.5 instead.

ack, picking this nice gem directly! :)

Comment 12 Roman Plevka 2021-06-22 14:56:40 UTC

VERIFIED on snap4
The network is brought up correctly and kickstart config is fetched and loaded.
Installation of rhel8.3 works

Comment 17 errata-xmlrpc 2021-07-01 14:56:48 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 (Satellite 6.9.3 Async Bug Fix Update), 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/RHBA-2021:2636