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.

Description of problem:
After installation, TFTP already contains grub.cfg deployed from outdate version of PXEGrub template:
[ see attachment "PXEGrub2_gd_old.txt"]

Despite the fact that the `pxegrub2_mac` snippet template looks different now:
[ see attachment "PXEGrub2_gd_new.txt"]


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

How reproducible:
always

Steps to Reproduce:
1. install satellite (with tftp and httpboot enabled)
2. check the rendered template:
   http://sat.fqdn:8000/httpboot/grub2/grub.cfg
3. Build PXE Default template
4. check the tempalte agani
5. observe the differences

Actual results:
grub.cfg contains outdated content (from old versions) until it is manually redeployed

Expected results:
The grub.cfg deployed by installer should correspond to the version present on satellite

Upstream bug assigned to lzap

Upstream bug assigned to lzap

Yes we have decided to require users to hit the Build PXE Default in order to boot unknown systems.

Verified on 6.8.0 Snap17.

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.8 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-2020:4366