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.
Created redmine issue https://projects.theforeman.org/issues/28343 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28343 has been resolved.
Verified in Satellite 6.8 snap 2
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