Red Hat Bugzilla – Bug 1318534
[RFE] Puppet classes inherited from a parent should indicate which one
Last modified: 2018-02-21 07:34:46 EST
1. Proposed title of this feature request - [RFE ]Puppet classes inherited from a parent should indicate which one 3. What is the nature and description of the request? - The existing host inherits puppet classes from a host group hierarchy. It would be helpful if the webui indicated the source of the inherited class. For example, /hosts/hostname.example.com/edit -> Puppet Classes The Included Classes column gives not hint about the source of the included classes. The tooltip is "Already included from parent". Could the module name be converted into a link to the parent resource? 4. Why does the customer need this? (List the business requirements here) 5. How would the customer like to achieve this? (List the functional requirements here) 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? 9. Is the sales team involved in this request and do they have any additional input? - NO 10. List any affected packages or components. 11. Would the customer be able to assist in testing this functionality if implemented? - Yes
Created redmine issue http://projects.theforeman.org/issues/14714 from this bug
Connecting redmine issue http://projects.theforeman.org/issues/14714 from this bug
Upstream bug component is Provisioning
Upstream bug component is Configuration Management
Upstream bug component is Puppet
Upstream bug assigned to sgraessl@redhat.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/14714 has been resolved.
Created attachment 1311165 [details] Form indicating the source of puppet classes Verified. Sat-6.3.0 snap 10
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-2018:0336