Bug #37707
closed
Passing --foreman-proxy-content-enable-docker false can leave smart_proxy_container_gateway in an inconsistent state
Added by Ewoud Kohl van Wijngaarden 5 months ago.
Updated 2 months ago.
Description
If smart_proxy_container_gateway was already installed on a host and then --foreman-proxy-content-enable-docker false
is used, it leaves it enabled but without Apache proxy config. On Foreman it'll also be reported as a feature. This is inconsistent.
- Status changed from New to Ready For Testing
- Assignee set to Ewoud Kohl van Wijngaarden
- Pull request https://github.com/theforeman/puppet-foreman_proxy/pull/843 added
- Pull request https://github.com/theforeman/puppet-foreman_proxy_content/pull/488 added
- Fixed in Releases 3.12.0 added
- Status changed from Ready For Testing to Closed
- Triaged changed from No to Yes
- Subject changed from Pasing --foreman-proxy-content-enable-docker false can leave smart_proxy_container_gateway in an inconsistent state to Passing --foreman-proxy-content-enable-docker false can leave smart_proxy_container_gateway in an inconsistent state
Also available in: Atom
PDF