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.
1. Feature Description:
After building a host from the satellite server, a rendered copy of the kickstart template will be saved in the host by the name "/root/original-ks.cfg".
Usually, the kickstart template of Satellite 6 doesn't have the required variable defined on the same to print the name of the template itself while it's being rendered against a host.
Due to the same, the file "/root/original-ks.cfg" won't also have the name of the kickstart template that was used for building the host.
This can be easily achieved by adding this segment of the code at the top of the kickstart template.
# Template Label: = <%= @template_name %>
2. Why does one need such a feature?
Usually, if someone using the Kickstart Default provisioning template, then it's not required but most people will clone this template and create some different model of templates to build different sets of host as per their application need.
If the above feature will be included, then one just need to login to the host which got build and they just can get the name of the template from the file "/root/original-ks.cfg" itself without any complications.
3. How customer can test and confirm the functionality ?
As a workaround to the Customer's query, It's already been tested and works just as explained.
VERIFIED
on sat.6.8.0-9
the "/root/original-ks.cfg" file on the built host now contains the information about its original template:
"# This kickstart file was rendered from the Foreman provisioning template "Kickstart default".
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