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
Per 6.3 planning, moving out non acked bugs to the backlog
Upstream bug component is Configuration Management
Upstream bug component is Provisioning
Upstream bug component is Smart Variables
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.