Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2174734 - Puppet environment not configured for Puppet agent during host Registration
Summary: Puppet environment not configured for Puppet agent during host Registration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.13.0
Assignee: Leos Stejskal
QA Contact: Gaurav Talreja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-02 10:35 UTC by Zuzana Lena Ansorgova
Modified: 2023-05-03 13:25 UTC (History)
2 users (show)

Fixed In Version: foreman-3.5.1.13-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 13:25:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36153 0 Normal Ready For Testing host_puppet_environment ignores host param 2023-03-02 10:35:51 UTC
Red Hat Issue Tracker SAT-16255 0 None None None 2023-03-02 15:06:55 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:25:23 UTC

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
Note You need to log in before you can comment on or make changes to this bug.