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 1287924 - katello-installer should also offer options to configure foreman-proxy settings
Summary: katello-installer should also offer options to configure foreman-proxy settings
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.1.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-03 01:21 UTC by jnikolak
Modified: 2019-09-26 13:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-23 16:27:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description jnikolak 2015-12-03 01:21:58 UTC 
1. Proposed title of this feature request  
katello-installer should also offer options to configure foreman-proxy settings

  
I need to configure foreman-proxy to start Puppet runs from Satellite web-ui. Currently I configure /etc/foreman-proxy/settings.d/puppet.yml manually. After every re-run of katello-installer this file will be overridden. 

It would be great if katello-installer would offer such configuration options for foreman-proxy settings during katello-installer run.

2. Who is the customer behind the request?  
Account: name and acct # <- please include both  
RED HAT, INC.

  
TAM customer: no/yes  no
SRM customer: no/yes  no
Strategic: no/yes  no
  
3. What is the nature and description of the request?  

New feature  


4. Why does the customer need this? (List the business requirements here)  

This will save time, without needing to re-apply custom settings.




5. How would the customer like to achieve this? (List the functional requirements here)  
 
n/a 

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  
  



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

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
  
n/a

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

yes  

10. List any affected packages or components.  

katello

  
11. Would the customer be able to assist in testing this functionality if implemented? 

Yes
Comment 2 Bryan Kearney 2016-07-08 20:46:26 UTC 
Per 6.3 planning, moving out non acked bugs to the backlog
Comment 4 Stephen Benjamin 2016-08-23 16:27:47 UTC 
This was delivered in 6.2. GA, all foreman-proxy options are now available, including the various puppet run options:

    --foreman-proxy-puppetrun     Enable puppet run/kick feature (default: true)
    --foreman-proxy-puppetrun-cmd  Puppet run/kick command to be allowed in sudoers (default: "/usr/bin/puppet kick")
    --foreman-proxy-puppetrun-listen-on  Puppet run proxy to listen on https, http, or both (default: "https")
    --foreman-proxy-puppetrun-provider  Set puppet_provider to handle puppet run/kick via mcollective (default: nil)
Note You need to log in before you can comment on or make changes to this bug.