Project

General

Profile

Actions

Bug #37707

closed

Pasing --foreman-proxy-content-enable-docker false can leave smart_proxy_container_gateway in an inconsistent state

Added by Ewoud Kohl van Wijngaarden 2 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Category:
Foreman modules
Target version:
-

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.

Actions #1

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
Actions #2

Updated by The Foreman Bot 2 months ago

  • Pull request https://github.com/theforeman/puppet-foreman_proxy_content/pull/488 added
Actions #3

Updated by The Foreman Bot about 2 months ago

  • Fixed in Releases 3.12.0 added
Actions #4

Updated by Ewoud Kohl van Wijngaarden about 2 months ago

  • Status changed from Ready For Testing to Closed
Actions #5

Updated by Ewoud Kohl van Wijngaarden about 1 month ago

  • Triaged changed from No to Yes
Actions

Also available in: Atom PDF