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 1396535 - [RFE] Incorporate required settings in puppet.conf without having to redo their config manually after every run of the satellite-installer.
Summary: [RFE] Incorporate required settings in puppet.conf without having to redo the...
Keywords:
Status: CLOSED DUPLICATE of bug 1305782
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-18 15:08 UTC by Vishwanath
Modified: 2020-12-14 07:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-18 17:05:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vishwanath 2016-11-18 15:08:14 UTC 
1. Proposed title of this feature request  
   Incorporate required settings in puppet.conf without having to redo their config manually after every run of the satellite-installer.
   
2. Who is the customer behind the request?  
  Account: NOMURA INTERNATIONAL PLC
  TAM customer: Yes
  SRM customer: No
  Strategic: Yes


3. What is the nature and description of the request? 
   After initial installation of Satellite/Capsule whenever satellite-installer command was run again in some scenarios eg: Satellite software upgrade, install custom SSL certificates. The /etc/puppet/puppet.conf was modified.


4. Why does the customer need this and how would the customer like to achieve this? ? (List the business and functional  requirements here)  
 This feature is requested as r10k is a standard tool came from Puppet and the customer wants a formally supported solution from Red Hat.
 Customer does not want to create his own workaround to address this issue.


5. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
 No.


6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
 No. Customer is addressing the issue by his own workaround right now.


7. Is the sales team involved in this request and do they have any additional input?  
 No.


8. List any affected packages or components.  
 NA.


9. Would the customer be able to assist in testing this functionality if implemented?  
 Yes.
Comment 2 Stephen Benjamin 2016-11-18 17:05:51 UTC 
The installer is puppet-based itself and manages a number of configuration files, including puppet itself.  That means any changes you make are overwritten on an installer run, e.g. for an upgrade.

In many cases, we provide installer options to change the configuration to meet your needs and in those cases your configuration will persist, but puppet is not currently one of them because it's called from inside another puppet class.

There's a few classes we indirectly use like puppet and apache.

We have a solution for these using hiera, where users are able to set *any*  parameter in a YAML file. That's BZ1305782. It will most likely be available for 6.3, but could end up earlier in a possible z-Stream.

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.

If for example, you want the agent to have a splay of 30, you would add this to custom-hiera.yaml:


  ---
  puppet::splaylimit: 30

You can look at /etc/foreman-installer/modules/puppet/manifests/init.pp to see what can be set for the puppet class. Nearly everything is configurable but if something isn't please file an RFE and we'll add it.


Thanks!

*** This bug has been marked as a duplicate of bug 1305782 ***
Note You need to log in before you can comment on or make changes to this bug.