Project

General

Profile

Actions
Copy link

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.

Status:
Closed
Priority:
Normal
Assignee:
Ewoud Kohl van Wijngaarden
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
https://github.com/theforeman/puppet-foreman_proxy/pull/843, https://github.com/theforeman/puppet-foreman_proxy_content/pull/488
Fixed in Releases:
Foreman - 3.12.0
Found in Releases:
Red Hat JIRA:
SAT-26903

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
Copy link
 #1

Updated by The Foreman Bot 5 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
Copy link
 #2

Updated by The Foreman Bot 5 months ago

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

Updated by The Foreman Bot 4 months ago

  • Fixed in Releases 3.12.0 added
Actions
Copy link
 #4

Updated by Ewoud Kohl van Wijngaarden 4 months ago

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

Updated by Ewoud Kohl van Wijngaarden 4 months ago

  • Triaged changed from No to Yes
Actions
Copy link
 #6

Updated by Ewoud Kohl van Wijngaarden 2 months ago

  • 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
Actions
Copy link

Also available in: Atom PDF