Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.
(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! :)
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