Bug #29450
closedSmart Proxy forces association to all Locations unless Puppet is enabled on the proxy
Description
Forum reference: https://community.theforeman.org/t/brand-new-smart-proxy-forces-association-with-almost-all-locations/17934
Problem: When creating a new Smart Proxy, with --puppet-server=false --foreman-proxy-puppet=false" --foreman-proxy-puppetca=false, the Smart Proxy gets bound to all Locations except Default Location, cannot assign it solely to the Location I need. The option to remove unwanted Locations is greyed out with “This is used by a host”.
Expected outcome: Be able to assign the proxy to Locations I select, not all.
Foreman and Proxy versions: 1.23.2
Distribution and version: CentOS 7.7 x86_64
Other relevant data:
If I enable either --foreman-proxy-puppet or --foreman-proxy-puppetca, then the Smart Proxy can be assigned to any Location.
I don't use Puppet, except for foreman-installer
Full foreman-installer command:
foreman-installer \
--scenario foreman-proxy-content \
--certs-tar-file "redacted" \
--foreman-proxy-content-parent-fqdn "redacted" \
--foreman-proxy-register-in-foreman "true" \
--foreman-proxy-foreman-base-url "redacted" \
--foreman-proxy-trusted-hosts "redacted" \
--foreman-proxy-trusted-hosts "redacted" \
--foreman-proxy-oauth-consumer-key "redacted" \
--foreman-proxy-oauth-consumer-secret "redacted" \
--puppet-server-foreman-url "redacted" \
--foreman-proxy-puppet=false \
--foreman-proxy-puppetca=false \
--foreman-proxy-tftp=false \
--puppet-server=false \
--foreman-proxy-content-enable-deb=true \
--foreman-proxy-content-enable-docker=false \
--foreman-proxy-content-enable-file=false \
--foreman-proxy-content-enable-puppet=false \
--foreman-proxy-content-enable-yum=false \
--foreman-proxy-templates=false