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
Updated by Ewoud Kohl van Wijngaarden over 4 years ago
- Project changed from Smart Proxy to Foreman
- Category changed from Plugins to Organizations and Locations
- Found in Releases 1.23.2 added
I think this is a bug in Foreman rather than the Proxy itself since only Foreman knows about organizations and locations.
Updated by dstephens1980 please_edit_me 10 months ago
- Found in Releases 3.7.1 added
Issue is still present in Foreman v3.7.1
Updated by dstephens1980 please_edit_me 10 months ago
Further info for for v3.7.1:
Newly created Smart Proxies show under Infrastructure -> Smart Proxies as bound to all locations, editing the Smart Proxy here results in the Locations being greyed out with note "This is used by a host." Navigating to Administer -> Locations and editing each individual location allows you to set the Smart Proxies but then the Infrastructure -> Smart Proxies page will randomly show either the Smart Proxies bound to all locations as per the above issue or will show them bound to their correct locations. Refreshing (F5) the Smart Proxies page will change what locations are shown as being bound. Real world use has shown that once the Administer -> Locations are changed then that location only uses the correct Smart Proxy regardless of what Infrastructure -> Smart Proxies shows.
Updated by The Foreman Bot 9 months ago
- Status changed from New to Ready For Testing
- Assignee set to Adam Ruzicka
- Pull request https://github.com/theforeman/foreman/pull/9976 added
Updated by Adam Ruzicka 4 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|94b341604bd81c409fc5a7e6ba2efc666ecaf14a.
Updated by Ewoud Kohl van Wijngaarden about 1 month ago
- Triaged changed from No to Yes