Bug 2174734

Summary:	Puppet environment not configured for Puppet agent during host Registration
Product:	Red Hat Satellite	Reporter:	Zuzana Lena Ansorgova <zuansorg>
Component:	Puppet	Assignee:	Leos Stejskal <lstejska>
Status:	CLOSED ERRATA	QA Contact:	Gaurav Talreja <gtalreja>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	pcreech, shwsingh
Target Milestone:	6.13.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-3.5.1.13-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-03 13:25:13 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 Zuzana Lena Ansorgova 2023-03-02 10:35:11 UTC

Description of problem:
The only way to configure Puppet agent during host registration is to use the host parameters puppet_server, puppet_ca_server and puppet_environment. While the Puppet servers appear in puppet.conf after the registration, the Puppet environment configuration key and value are missing.


Version-Release number of selected component (if applicable): N/A


How reproducible: always


Steps to Reproduce:
1. Set global host parameters: enable-puppet7, puppet_server, puppet_ca_server, and puppet_environment
2. Register the host with Puppet agent provided in an activation key.
3. Check puppet.conf on the host.

Actual results:

puppet.conf contains "server" and "ca_server" config values, but not the "environment" key and value.

Expected results:

puppet.conf should contain also "environment" with the value defined in the "puppet_environment" host parameter.

Additional info:

Comment 1 Brad Buckingham 2023-03-02 15:06:28 UTC

Is this a regression from 6.12?  Thanks!

Comment 2 Zuzana Lena Ansorgova 2023-03-06 09:33:14 UTC

No, it isn't a regression.

Comment 3 Bryan Kearney 2023-03-09 16:03:20 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36153 has been resolved.

Comment 5 Gaurav Talreja 2023-03-21 20:41:25 UTC

Verified.

Tested on Satellite 6.13.0 Snap 15.0
Version: foreman-3.5.1.13-1.el8sat.noarch

Steps:
1. Prepare puppet enabled Satellite, sync kickstart repos, and client repo for provisioning
2. Create a host with mentioned host params for provisioning or select the environment
OR Create a host group with mentioned host params and use it for host registration
3. Verify value specified in puppet_environment host param is set for an environment in puppet.conf on the host under the agent section

Observation:
puppet.conf on the host, contains the "environment" field which is set with the "puppet_environment" host parameter or with environment selected in host creation
For non-integrated Puppet, I check this issue isn't reproducible for older snaps and works fine there and with the latest snap, checked with a reporter and she mentioned this issue could be with only puppet integrated setup

Comment 8 errata-xmlrpc 2023-05-03 13:25:13 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.13 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:2097