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.

Description of problem:
IHAC who want to be able to set the values for the two boolean puppet.conf variables, stringify_facts and trusted_node_data in the satellite environment (both for the satellite server and the capsules). Manually made changes to the file do not persist across different satellite-installer runs. Can we provide a way through satellite installer such that the changes made will persist.

Version-Release number of selected component (if applicable):
Satellite 6.2

How reproducible:
Every time

Steps to Reproduce:
1. Edit the /etc/puppet/puppet.conf file on the Satellite with some settings examples see below
---
[master]
...
    trusted_node_data = true
...
---

2. Run the satellite-installer

3. Verify whether the setting is stil there

Actual results:
Settings do not persist

Expected results:
Settings should persist

Dupe. See https://bugzilla.redhat.com/show_bug.cgi?id=1305782#c14 and comments 15 and 16 for an understanding of how this works, but you'll be able to configure any of the options you want in 6.3.  


The custom-hiera.conf would look like:


---
puppet::server_additional_settings:
  - trusted_node_state: true
agent_additional_settings:
  - stringify_facts: true

*** This bug has been marked as a duplicate of bug 1305782 ***

Actually:

---
puppet::server_additional_settings:
  - trusted_node_state: true
puppet::agent_additional_settings:
  - stringify_facts: true