Project

General

Profile

Bug #28343

Incorrect example to use multiple attributes as a matcher key in the tooltip for Order

Added by yifat makias 9 months ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Parameters
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1772381

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.

Associated revisions

Revision 2832e49b (diff)
Added by yifat makias 9 months ago

Fixes #28343 - fixed order info example for multiple attributes

History

#1 Updated by The Foreman Bot 9 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/7204 added

#2 Updated by The Foreman Bot 9 months ago

  • Fixed in Releases 2.0.0 added

#3 Updated by yifat makias 9 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF