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.
DescriptionFred van Zwieten
2015-09-29 11:59:58 UTC
Description of problem:
When creating a new host, class parameters that match on a smart class parameter match value do not show the match before the new host is created. It does show after the host is created. This means the user is not able to view the actual value chosen before the host is created and thus cannot decide if this is the correct value or that it should override it for this host.
Version-Release number of selected component (if applicable):
How reproducible:
Create smart class parameter with override enabled and a matcher on i.e. domain
Open dialog new host to create new host making sure the matcher should match
Go to parameters and see what the chosen value is
Steps to Reproduce:
1.
2.
3.
Actual results:
chosen value is empty
Expected results:
is should show the chosen value
Additional info:
Apperantly, it resolves these matchers during host creation, but imho that is too late.
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/RHBA-2016:1501