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.
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.
Moving to POST since upstream bug http://projects.theforeman.org/issues/7163 has been closed
-------------
Anonymous
Applied in changeset commit:04c6b0197e93f6c8a616c8695260bcd01563d044.
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
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