Bug #15999
Unable to use foreman-installer -S capsule and not enable puppet and pulp as proxy items
Description
I was trying to set up a capsule to run dhcp and realm plugins without anything else on my IPA server.
I tried foreman-installer -S capsule --capsule-parent-fqdn "hostname" --foreman-proxy-register-in-foreman true --foreman-proxy-foreman-base-url "https://hostname" --foreman-proxy-trusted-hosts `hostname` --foreman-proxy-oauth-consumer-key "key" --foreman-proxy-oauth-consumer-secret "secret" --capsule-pulp-oauth-secret "secret" --capsule-certs-tar "/tmp/files.tar" --foreman-proxy-realm true --foreman-proxy-dhcp true--foreman-proxy-puppetca false as my base to set things with --foreman-proxy-plugin-pulp-enabled false , --no-foreman-proxy-plugin-pulp-enabled, --no-foreman-proxy-plugin-pulpnode-enabled false
None of those options seemed to affect whether pulp was enabled or not.
I also couldn't even find an option that wouldn't enable puppet.
History
#1
Updated by Dominic Cleal almost 6 years ago
Updated by - Project changed from Installer to Katello
#2
Updated by Eric Helms almost 6 years ago
Updated by - Status changed from New to Need more information
Hi Leah,
I would think that '--foreman-proxy-plugin-pulpnode-enabled false' should prevent Pulp from being installed. And --capsule-puppet false should turn off Puppet. This is on a 3.X installation.
#3
Updated by Leah Fisher almost 6 years ago
Updated by I would have thought these things as well, but they don't seem to make any difference. This is on the 3.0.2 installation and foreman 1.11.3.
#4
Updated by Justin Sherrill over 5 years ago
Updated by - Assignee set to Eric Helms
#5
Updated by Justin Sherrill over 5 years ago
- Status changed from Need more information to New
- Assignee deleted (
Eric Helms) - Legacy Backlogs Release (now unused) set to 114