Red Hat Bugzilla – Bug 1142160
Unable to use cloned PXELinux global default template with 6.0.4
Last modified: 2017-02-23 15:57:40 EST
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
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).
Created redmine issue http://projects.theforeman.org/issues/7480 from this bug
Upstream bug assigned to stbenjam@redhat.com
Moving to POST since upstream bug http://projects.theforeman.org/issues/7480 has been closed ------------- Dominic Cleal Katello should not be locking core Foreman templates: https://github.com/Katello/katello/blob/katello-2.0.0-0/db/seeds.rb#L39-L44 ------------- Stephen Benjamin > Katello should not be locking core Foreman templates: https://github.com/Katello/katello/blob/katello-2.0.0-0/db/seeds.rb#L39-L44 I disagree. Foreman should be locking core templates, so that you can update them at will, but you're stuck due to precedence. In a multi-org and multi-loc setup, having the core templates editable is just totally broken. ------------- Anonymous Applied in changeset commit:katello|268ea646bcc163956b73ae7c474f386774902550.
To test this, just confirm you edit "PXELinux global default" config template in the UI. It should be unlocked in 6.1.
This bug is slated to be released with Satellite 6.1.
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