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.
Since "PXELinux global default" template is locked and the name is hardcoded in Foreman codebase, there is no way to use Foreman Discovery since we can't configure initial boot.
Workaround: Unlock the locked template and edit it.
# foreman-rake console
> ct = ConfigTemplate.find_by_name("PXELinux global default"); ct.locked = false; ct.save!
> exit
Comment 1RHEL Program Management
2014-09-16 09:33:21 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
It looks like there are two options to do:
A) Implement a global settings for all hardcoded template names. This is easy to do.
B) Implement these settings per-subnet which adds more granularity but it is more complicated.
We can implement both A+B (A as a fallback when B is not specified per-subnet).
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, 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-2015:1592
Since "PXELinux global default" template is locked and the name is hardcoded in Foreman codebase, there is no way to use Foreman Discovery since we can't configure initial boot. Workaround: Unlock the locked template and edit it. # foreman-rake console > ct = ConfigTemplate.find_by_name("PXELinux global default"); ct.locked = false; ct.save! > exit