Project

General

Profile

Actions

Bug #15999

closed

Unable to use foreman-installer -S capsule and not enable puppet and pulp as proxy items

Added by Leah Fisher over 7 years ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

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.

Actions

Also available in: Atom PDF