Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Provisioning templates association for Host Group and Environment Combinations is not honored, when templates are determined at the time of host creation
Description of problem:
Provisioning templates restriction for Valid Host Group and Environment Combinations is not honored, when templates are determined at the time of host creation
Version-Release number of selected component (if applicable):
v.6.6.2
How reproducible:
Easily reproducible
Steps to Reproduce:
1. 2 Host Groups HGA and HGB
2. 2 Custom Provisioning Templates TemplateA and TemaplateB
3. 2 Puppet Environment : Env1 and Env2
3. Default Provisioning Template : Kickstart Default
4. Operating System : RedHat 8.1 OR any
Steps :
1. Associate Default Provisioning Template, with Operating System : RedHat 8.1
Host --> Operating System --> RedHat 8.1 --> Templates --> Provisioning template --> Set it to Kickstart Default
2. Associate TemplateA with HGA and Env1:
Hosts --> Provisioning Templates -> TemplateA --> Association --> Ensure "Applicable Operating Systems" as RedHat 8.1 AND click on +Add Combination for "Valid Host Group and Environment Combinations" --> Host Group as HGA and Env1
3. Associate TemplateB with HGB and Env2:
Hosts --> Provisioning Templates -> TemplateB --> Association --> Ensure "Applicable Operating Systems" as RedHat 8.1 AND click on +Add Combination for "Valid Host Group and Environment Combinations" --> Host Group as HGB and Env2
4. Now when we try create a host with RedHat 8.1 Operating System with "HGA" or HGB, it DOES NOT renders correct Provisioning Template
Actual results:
1. Irrespective of whichever Host Group we use, always a default provisioning template is rendered i.e "Kickstart Default"
Expected results:
Whenver we use HGA for host creation, it should honor association of template and use TemplateA provisioning template and vice versa.
Additional info:
Provisioning Templates association works correctly, when we associate with ONLY Host Group and setting Environment as "None".
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.