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.
This appears to be in at least Satellite 6.13 SNAP 3; therefore, aligning to the release for QE verification.
# rpm -qa|grep bootload|grep 202102220000
foreman-bootloaders-redhat-202102220000-1.el8sat.noarch
foreman-bootloaders-redhat-tftpboot-202102220000-1.el8sat.noarch
From the upstream page:
These bootloaders were used in Foreman 1.15-1.16 and are no longer in active use or development. Foreman installer now generates grub2 image via grub2-mknetdir command and it is possible to do this on Red Hat systems for multiple architectures. Other bootloaders like grub1 or pxelinux must be acquired from upstream projects.
https://github.com/theforeman/foreman-bootloaders
Please check and remove this package from Satellite. On a clean deployment, check if this package is not installed at all, it should not be. If it is present, try to install Satellite with this package blocked via yum blocklist, if puppet installer still installs it we should drop this.
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 (Important: Satellite 6.13 Release), 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-2023:2097