Bug 1247625

Summary:	Selecting other hostgroup when creating new host does not update Puppet Environment
Product:	Red Hat Satellite	Reporter:	Maxim Burgerhout <mburgerh>
Component:	Host Group	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	bbuckingham, bkearney, cwelton
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	edit hostgroup: puppet env does not change, cv does edit hostgroup: puppet classes screen now empty
Last Closed:	2017-01-11 19:36:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Maxim Burgerhout 2015-07-28 13:15:47 UTC

Description of problem:
Selecting a different hostgroup while creating a new host updates the content view, but it does not update the Puppet Environment.

Version-Release number of selected component (if applicable):
6.1.0 beta
foreman-1.7.2.32-1.el7sat.noarch

How reproducible:

Steps to Reproduce:
1. Open 'New Host' dialogue
2. Select Hostgroup A
3. Change that to Hostgroup B

Actual results:
Content view changes to the one belonging to Hostgroup B, Puppet Environment still reflects the Puppet Environment associated with the content view belonging to Hostgroup A

Expected results:
Both the content view and the Puppet Environment change to the default belonging to Hostgroup B

Additional info:

Comment 3 Bryan Kearney 2017-01-11 19:36:53 UTC

This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.