Bug 1998718

Summary:	puppet environment is not created from satellite webui
Product:	Red Hat Satellite	Reporter:	Ram Nainsingh Tiruwa <ramsingh>
Component:	Puppet	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.10.0	Keywords:	Triaged
Target Milestone:	Unspecified
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:	2023-04-06 17:10:05 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 Ram Nainsingh Tiruwa 2021-08-28 08:51:48 UTC

Puppet Environment is not created from satellite webUI

Red Hat Satellite 6.10

How reproducible:

Login to Satellite webui -> Confiure -> Puppet Environments -> Create Puppet Environment

It will create Environment, but when trying to import Environment From satellite it shows "Environmet-name Remove:	Deleted environment"

Actual results:
It should import the Environment and the Environment should be created in satellite Filesystem which is not.

We need to create the Environment manually in /etc/puppetlabs/code/environments

After creating we are able to see the Environment properly

Comment 1 Brad Buckingham 2021-08-30 13:09:33 UTC

Is this a regression from Satellite 6.9?

Comment 2 Marek Hulan 2021-09-03 09:17:29 UTC

This is not the regression and it's also expected behavior. Environments created manually in Foreman not get created on the Puppet server. Satellite only created such environment for modules maintained in content view, but that funtionality is dropped in 6.10. The syncrhonization for non-content views Puppet environments was always one way Puppet server -> Satellite. The reason is, people typically create the env manually in /etc/puppetlabs/code/environments and upload classes in there. Environments are normally created by syncing the information from the Puppet server. The reason we have "Create Puppet Environment" button in Satellite is, that in early versions of Foreman the syncing was not possible. We kept it then in case manual intervention is needed. Given this whole funtionality is being removed in 7.0, I think this should be closed as WONTFIX.

Comment 3 Marek Hulan 2021-09-23 12:20:00 UTC

*** Bug 1870362 has been marked as a duplicate of this bug. ***

Comment 4 Marek Hulan 2021-09-23 12:20:25 UTC

Also this seems to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1870362, closing that since this has now more information

Comment 6 Brad Buckingham 2023-03-06 11:38:36 UTC

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.

Comment 7 Brad Buckingham 2023-04-06 17:10:05 UTC

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.