Bug 1393871

Summary:	[RFE] Changing host environment in webUI should change host's defined environment in puppet.conf
Product:	Red Hat Satellite	Reporter:	Rick Dixon <rdixon>
Component:	Puppet	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.2.3	CC:	bbuckingham, bkearney, kelly.brown1, ohadlevy, rdixon
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-24 20:26:03 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:

Description Rick Dixon 2016-11-10 13:51:25 UTC

Description of problem:

Changing a host's environment via the Satellite 6 webUI does not seem to change the specified environment in puppet.conf, leading to output such as "Could not find environment X, now switching to environment Y". It does seem to switch to the correct environment, but why would this not overwrite the old environment in puppet.conf?


How reproducible:

Always.


Steps to Reproduce:
1. Explicitly assign a host to environment X in /etc/puppet.puppet.conf
2. Switch the host to a new environment via the Satellite webUI
3. Trigger a puppet agent run; the old environment stays defined in puppet.conf, resulting in output complaining about the old environment.


Actual results:

Puppet agent complains that the old environment can't be found.


Expected results:

This parameter in puppet.conf should be updated to reflect the specified new environment in the Satellite webUI

Comment 2 Kelly 2016-11-14 13:43:39 UTC

By running into the issue, I found that if you remove the old environment puppet stops working for the clients with that environment set.  Since the system never updates the puppet.conf but simply overrides with what's in satellite, you could eventually end up in a situation where many clients need to be updated outside of the system if the original puppet environment is completely removed.

Comment 3 Ohad Levy 2016-11-15 21:29:20 UTC

do you actually manage puppet.conf via puppet? its up to the user to decide he/she wants to manage the file. further when the enc output defines a puppet environments, the clients uses that environment over whatever is defined in puppet.conf.

Comment 4 Kelly 2016-11-16 13:27:33 UTC

I guess it depends on how you're using puppet.  From my perspective ( end user/purchaser of Satellite ), Satellite installed puppet.  It provides a way for me to change the environment within the UI.  And then if I remove the old environment later, it breaks.  Either puppet is integrated or it's not.  Again, end user take on it.

Comment 5 Bryan Kearney 2017-08-24 20:26:03 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.