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".