Bug 1772381

Summary: Incorrect example to use multiple attributes as a matcher key in the tooltip for Order
Product: Red Hat Satellite Reporter: Sergei Petrosian <spetrosi>
Component: Smart VariablesAssignee: Yifat Makias <ymakias>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: egolov, inecas, mshira, orabin
Target Milestone: 6.8.0Keywords: EasyFix, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-2.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:59:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
An example of how to match on multiple attributes none

Description Sergei Petrosian 2019-11-14 09:55:55 UTC
Created attachment 1636076 [details]
An example of how to match on multiple attributes

Description of problem:
A tooltip provides an incorrect example on how to use multiple attributes as a matcher key.

Version-Release number of selected component (if applicable):
Satellite 6.4 and later
Foreman 1.10 and later

How reproducible:
Always

Steps to Reproduce:
1. In the Satellite web UI, navigate to *Configure* > *Puppet Classes*.
2. Select a class.
3. Click *Smart Class Parameter*.
4. Select some parameter and select the *Override* check box.
5. Click *Add Matcher*.
6. Click on the tooltip next to "Order".
7. Find the following text:
The order in which matchers keys are processed, first match wins.
You may use multiple attributes as a matcher key, for example, an order of host group, environment would expect a matcher such as hostgroup = "web servers", environment = production

Actual results:
The tooltip is misleading. 
1. The example says “host group, environment”, but host group should be hostgroup (spaces don’t work) and the comma needs to be removed. The correct example would be “hostgroup,environment”.

when a space is added after the comma in the ‘Order’-box as the tooltip suggests it is not working.

Expected results:
Something like this. Please correct me if I am wrong:
The order in which matchers keys are processed, first match wins.
You may use multiple attributes as a matcher key, for example, an order of `host group,environment` would expect a matcher such as `hostgroup-"web servers",environment-production

Additional info:
You can find the working setup in the attachment.

Comment 3 Yifat Makias 2019-11-25 12:49:10 UTC
Created redmine issue https://projects.theforeman.org/issues/28343 from this bug

Comment 4 Bryan Kearney 2019-11-26 15:00:38 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28343 has been resolved.

Comment 7 Peter Ondrejka 2020-06-05 08:33:08 UTC
Verified in Satellite 6.8 snap 2

Comment 10 errata-xmlrpc 2020-10-27 12:59:33 UTC
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 (Important: Satellite 6.8 release), 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-2020:4366