Actions
Bug #37707
closedPasing --foreman-proxy-content-enable-docker false can leave smart_proxy_container_gateway in an inconsistent state
Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Yes
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.
Updated by The Foreman Bot 2 months ago
- 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
Updated by The Foreman Bot 2 months ago
- Pull request https://github.com/theforeman/puppet-foreman_proxy_content/pull/488 added
Updated by Ewoud Kohl van Wijngaarden about 2 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman_proxy_content|ac878a031bfbf09fb7139df04ddd5a8857edb4ce.
Updated by Ewoud Kohl van Wijngaarden about 1 month ago
- Triaged changed from No to Yes
Actions