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.
DescriptionJitendra Yejare
2016-01-19 09:38:24 UTC
Description of problem:
Currently If we are trying to add matcher for 'non existing attribute' in Smart Class Parameter/Smart Variables it raises as error 'Match <attribute_name> = <value> does not match an existing <attribute_name> ' and this is only applicable when attributes are FQDN/HostGroup. It seems this doesn't work / not added for other attributes such as OS, domain etc.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create a matcher for non existing attribute(other than FQDN, HostGroup) for smart class parameter / variable other.
2. Attempt to submit.
Actual results:
No Error raised for Attribute not existing in satellite.
Expected results:
Error should be raised for non existence of attribute and for all the attributes.
Additional info:
I believe this is done by design, to be able to specify the matcher even for cases where the data are not yet available, but we expect them to appear in the system later (when facts are uploaded from hosts). We can change the RFE to warn (but not prevent) from saving the smart variables, in which case we would not even had distinguish between fqdn/hostgroup and something else. Anyway, proposing for 6.3 as it's not something we would commit for 6.2
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.