Red Hat Bugzilla – Bug 1166158
[RFE] In host's edit page, show the source for the value of puppet class parameters
Last modified: 2017-02-23 15:47:39 EST
Opened as a PR by breakfastattiffs Currently, on the edit hosts page, under the parameters tab, if a parameter was overridden in the host's hostgroup (or that hostgroup's hostgroup), the additional information popup for that parameter says "Matcher: hostgroup." This is not very useful because the parameter's value could be coming from the hostgroup or a grandparent hostgroup. It would be more useful to display the actual hostgroup's name so that we know precisely from which parent the parameter's overridden value is coming from.
Created from redmine issue http://projects.theforeman.org/issues/7163
I am pulling down important features from the 1.7 release. You can read more abotu this feature at http://theforeman.org/manuals/1.7/index.html#Releasenotesfor1.7 I believe that QE will be done by the community on this feature.
Moving to POST since upstream bug http://projects.theforeman.org/issues/7163 has been closed ------------- Anonymous Applied in changeset commit:04c6b0197e93f6c8a616c8695260bcd01563d044.
Can someone please help to share the steps to test this out ?
Created attachment 1000350 [details] Assuming additional_info box will show the source with hostgroup name, as from where the value is coming
As per comment8, the info box shows the activation key's source name is sgroup to which the key associated first. Is there anything else QE needs to validate ?
Thanks Bryan, I got the info from this PR: https://github.com/theforeman/foreman/pull/1667 So looks like its working as expected. As per comment 8, I can see the hostgroup name. Verified with: sat6.1 beta snap5 Satellite-6.1.0-RHEL-7-20150303.0
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