Bug 1299789 - [RFE] Error for Non Existing attribute while adding Matcher.
[RFE] Error for Non Existing attribute while adding Matcher.
Status: NEW
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Smart Variables (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: Unspecified
: --
Assigned To: satellite6-bugs
Katello QA List
: FutureFeature, Triaged
Depends On:
Blocks: 1278718
  Show dependency treegraph
Reported: 2016-01-19 04:38 EST by Jitendra Yejare
Modified: 2018-05-09 02:43 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 13271 None None None 2016-04-22 10:56 EDT

  None (edit)
Description Jitendra Yejare 2016-01-19 04:38:24 EST
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:

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:
Comment 3 Ivan Necas 2016-04-26 08:34:02 EDT
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
Comment 4 Bryan Kearney 2016-07-08 16:41:11 EDT
Per 6.3 planning, moving out non acked bugs to the backlog
Comment 6 Bryan Kearney 2016-08-10 15:12:58 EDT
Upstream bug component is Configuration Management
Comment 7 Bryan Kearney 2016-08-10 16:13:57 EDT
Upstream bug component is Provisioning
Comment 8 Bryan Kearney 2016-08-10 18:13:36 EDT
Upstream bug component is Configuration Management
Comment 9 Bryan Kearney 2016-08-12 08:51:22 EDT
Upstream bug component is Smart Variables

Note You need to log in before you can comment on or make changes to this bug.