Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1384009 - [RFE] using smart variables based on Host Collections
Summary: [RFE] using smart variables based on Host Collections
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Smart Variables
Version: 6.2.2
Hardware: All
OS: All
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
: 1391824 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-12 11:03 UTC by Anand Agrawal
Modified: 2021-06-10 11:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-05 17:06:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 orabin 2016-12-29 09:53:09 UTC
*** Bug 1391824 has been marked as a duplicate of this bug. ***

Comment 2 orabin 2017-01-19 12:57:29 UTC
A host can be in more then one host collection.

If there is a host in host collection A and host collection B, and there was a possibility to add these matchers:
host_collection=A will get the value A
host_vollection=B will get the value B
which value should the host get? A or B?

In smart variables you can define the order of which value to use but it's by the type in the matcher e.g if these matchers are defined:
hostgroup=My_hostgroup will get value A
os=My_os will get value B
and a host has hostgoup My_hostgroup and os My_os then for the order: hostgroup,os 
the host will get value A 
and for the order: os,hostgroup 
the host will get value B.

The order creates a priority of which value to use but if host_collection is added to the order there is still no way to prioritize when a host is connected to more then one host collection.

Comment 7 Bryan Kearney 2017-09-05 17:06:12 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Customers can use custom facts on the machine to drive this sort of robust logic in the puppet classes.


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