Bug 1766136

Summary:	[DDF] This seems to be outdated for Satellite 6.3>, as the parameter has been changed to a drop-down box.
Product:	Red Hat Satellite	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	Documentation	Assignee:	Sergei Petrosian <spetrosi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Melanie Corr <mcorr>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	oprazak, spetrosi, vgrosu
Target Milestone:	Unspecified	Keywords:	Reopened
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-02 10:18:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2019-10-28 11:54:58 UTC

This seems to be outdated for Satellite 6.3>, as the parameter has been changed to a drop-down box.
As a result of this change it seems to be impossible use multiple attributes as a matcher key, as described in the (i)-pop-up of the Order-field within Satellite that says: `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`. Description of this functionality is totally missing within the documentation.

Reported by: gertjan.bijl_keylanehosting

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.5/html/puppet_guide/chap-red_hat_satellite-puppet_guide-adding_puppet_modules_to_red_hat_satellite_6#annotations:66d81aad-c564-4fbb-a905-362d155e5c62

Comment 1 Sergei Petrosian 2019-11-13 09:55:29 UTC

Hello,

Thank you for raising this bug.

Comment 2 Sergei Petrosian 2019-11-14 10:14:36 UTC

I have contacted the reporter and with all the information provided, we came to the conclusion that the example in the tooltip is incorrect. oprazak found what is the correct configuration and shared it with me. You can find the correct configuration for using multiple attributes as a matcher key in the attachment 1636076 [details].

I have opened BZ#1772381 to fix the misleading examples in the "Order" tooltip. You can find the attachment 1636076 [details] that provides the correct configuration for using multiple attributes as a matcher key.

I will add a note to the doc that until BZ#1772381 is resolved, the example in the tooltip is incorrect and what is the correct configuration.

Comment 9 Sergei Petrosian 2019-11-22 15:43:24 UTC

These changes are now live on the customer portal:

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.6/html/puppet_guide/chap-red_hat_satellite-puppet_guide-adding_puppet_modules_to_red_hat_satellite_6#sect-Red_Hat_Satellite-Puppet_Guide-Adding_Puppet_Modules_to_Red_Hat_Satellite_6-Configuring_Smart_Class_Parameters

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.5/html/puppet_guide/chap-red_hat_satellite-puppet_guide-adding_puppet_modules_to_red_hat_satellite_6#sect-Red_Hat_Satellite-Puppet_Guide-Adding_Puppet_Modules_to_Red_Hat_Satellite_6-Configuring_Smart_Class_Parameters

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html/puppet_guide/chap-red_hat_satellite-puppet_guide-adding_puppet_modules_to_red_hat_satellite_6#sect-Red_Hat_Satellite-Puppet_Guide-Adding_Puppet_Modules_to_Red_Hat_Satellite_6-Configuring_Smart_Class_Parameters

Comment 11 Ondřej Pražák 2019-11-28 14:29:31 UTC

Hi Sergei,
the second example is correct, in the field should be Default_Location,development