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.
Bug 1919400 - Cannot build a RHEL 8.3 system via Satellite Full Host Bootdisk
Summary: Cannot build a RHEL 8.3 system via Satellite Full Host Bootdisk
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.7.0
Hardware: x86_64
OS: Linux
high
unspecified
Target Milestone: 6.8.4
Assignee: Lukas Zapletal
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-22 19:19 UTC by James Jeffers
Modified: 2024-06-14 00:00 UTC (History)
16 users (show)

Fixed In Version: foreman-2.1.2.25-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1903247
Environment:
Last Closed: 2021-02-24 12:47:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31452 0 Urgent Closed Cannot build an EL 8.3 system via Satellite Bootdisk or Discovery kexec 2021-02-15 15:06:21 UTC
Foreman Issue Tracker 31573 0 Normal Closed Drop IPAPPEND2 completely and use 01 for the hardware prefix 2021-02-15 15:06:22 UTC
Red Hat Knowledge Base (Solution) 5631571 0 None None None 2021-01-22 19:19:41 UTC
Red Hat Product Errata RHBA-2021:0654 0 None None None 2021-02-24 12:47:36 UTC

Comment 6 Roman Plevka 2021-02-11 12:26:41 UTC
Verified
on sat6.8.4-1.0

i was able to successfully provision a rhel8.3 host using the following flow:
- sync rhel8.3 repos
- add vmware as a compute resource
- create new host using the compute resource and "boot disk" provisioning method
  - satellite generates the full host boot disk iso and automatically uploads it to vmware store + attaches it to the newly created VM
- machine successfully booted the iso and loaded all the files via ipxe
- anaconda successfully installed all the packages
- RHEL8.3 successfully booted up after reboot.

Comment 11 errata-xmlrpc 2021-02-24 12:47:13 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.8.4 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:0654

Comment 12 James Hartsock 2021-04-15 23:46:25 UTC
I show satellite upgrade corrects kickstart, but not kexec templates as customer pointed out in Red Hat Customer Portal Solution comment too!

So on sat 6.8.1 instance I had
# mkdir /var/tmp/6.8.1/
# for id in $(hammer template list | awk '/^[0-9]/ {print $1}'); do hammer template dump --id ${id} > /var/tmp/6.8.1/template.${id}; done
# egrep '^name|bootif.*00-' $(grep -l bootif.*00- /var/tmp/6.8.1/template.*)
/var/tmp/6.8.1/template.137:name: Discovery Red Hat kexec
/var/tmp/6.8.1/template.137:  bootif = '00-' + mac.gsub(':', '-') if mac
/var/tmp/6.8.1/template.138:name: Discovery Debian kexec
/var/tmp/6.8.1/template.138:  bootif = '00-' + mac.gsub(':', '-') if mac
/var/tmp/6.8.1/template.22:name: kickstart_kernel_options
/var/tmp/6.8.1/template.22:    bootif = '00-' + mac.gsub(':', '-')

Do upgrade
# satellite-maintain upgrade check --target-version 6.8.z
# satellite-maintain upgrade run --target-version 6.8.z

And on 6.8.6 instance now I have:
# mkdir /var/tmp/6.8.6/
# for id in $(hammer template list | awk '/^[0-9]/ {print $1}'); do hammer template dump --id ${id} > /var/tmp/6.8.6/template.${id}; done
# egrep '^name|bootif.*00-' $(grep -l bootif.*00- /var/tmp/6.8.6/template.*)
/var/tmp/6.8.6/template.137:name: Discovery Red Hat kexec
/var/tmp/6.8.6/template.137:  bootif = '00-' + mac.gsub(':', '-') if mac
/var/tmp/6.8.6/template.138:name: Discovery Debian kexec
/var/tmp/6.8.6/template.138:  bootif = '00-' + mac.gsub(':', '-') if mac

Comment 13 Lukas Zapletal 2021-04-19 08:04:41 UTC
That is right, I forgot about discovery workflows. The errata shipped with only bootdisk fixes.

I am creating a new BZ for this:

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

Comment 14 Lukas Zapletal 2021-04-19 08:20:35 UTC
Please use a template change as a workaround until we ship fix for discovery kexec.


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