Bug 1697476

Summary: [RFE] To be able to see the name of the provisioning template being used to build a host from the host itself
Product: Red Hat Satellite Reporter: Sayan Das <saydas>
Component: Provisioning TemplatesAssignee: Leos Stejskal <lstejska>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: medium Docs Contact:
Priority: high    
Version: 6.4CC: bkearney, egolov, lstejska, mhulan
Target Milestone: 6.8.0Keywords: EasyFix, FutureFeature, Triaged
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: foreman-2.1.0-0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:58:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sayan Das 2019-04-08 13:45:58 UTC 
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.
Comment 4 Leos Stejskal 2020-01-30 08:12:17 UTC 
Created redmine issue https://projects.theforeman.org/issues/28896 from this bug
Comment 5 Bryan Kearney 2020-02-13 13:05:06 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28896 has been resolved.
Comment 6 Roman Plevka 2020-07-27 11:34:54 UTC 
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".
Comment 9 errata-xmlrpc 2020-10-27 12:58:35 UTC 
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