Bug #5799
closed
Using Foreman-Installer to install Puppet Master / Smart Proxy only configuration
Added by Derek Wright over 10 years ago.
Updated over 10 years ago.
Description
After the install an edit is needed to /etc/puppet/node.rb and url = needs to be https. Also when the flag to enable-puppetca = false, the smart proxy is still being set to manage puppet ca certs. I had to manually set this to false and reload services.
Here are the installer flags used (taken from manual)
foreman-installer \
--no-enable-foreman \
--no-enable-foreman-plugin-bootdisk \
--no-enable-foreman-plugin-setup \
--enable-puppet \
--puppet-server-ca=false \
--puppet-server-foreman-url=http://foreman.example.com \
--enable-foreman-proxy \
--foreman-proxy-tftp=false \
--foreman-proxy-foreman-base-url=http://foreman.example.com \
--foreman-proxy-oauth-consumer-key=<key here> \
--foreman-proxy-oauth-consumer-secret=<secret here>
OK, found another spot where i needed to fix http->https in reports/foreman.rb so puppet will upload reports. However it seems that the cli switch is just taking the http://foreman url info I gave it, that probably should have been https://foreman. Perhaps the documentation can be updated to make that clear?
- Project changed from Foreman to Website
- Status changed from New to Closed
- Assignee set to Dominic Cleal
- % Done changed from 0 to 100
Thanks for the report. I've updated the command to this:
foreman-installer \
--no-enable-foreman \
--no-enable-foreman-plugin-bootdisk \
--no-enable-foreman-plugin-setup \
--enable-puppet \
--puppet-server-ca=false \
--puppet-server-foreman-url=https://foreman.example.com \
--enable-foreman-proxy \
--foreman-proxy-puppetca=false \
--foreman-proxy-tftp=false \
--foreman-proxy-foreman-base-url=https://foreman.example.com \
--foreman-proxy-oauth-consumer-key=<key here> \
--foreman-proxy-oauth-consumer-secret=<secret here>
Also available in: Atom
PDF
Updated by 
Updated by