Project

General

Profile

Bug #31662

Foreman content proxy doesn't listen on port 80 anymore

Added by Gerald Vogt 3 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
No
Bugzilla link:

Description

Upgrading from katello 3.17 to katello 3.18.1, foreman 2.2 to 2.3.1 it seems my content proxy server doesn't listen to port 80 anymore. I have a seperate server running only the content proxy for my clients. After upgrade it's not listening to port 80, which breaks (among other things) provisioning through those proxys as the server hosting the tftp server tries to retrieve the vmlinuz etc. via port 80 from the proxy.

See also https://community.theforeman.org/t/content-proxy-not-listing-to-port-80-anymore/21996

Associated revisions

Revision 2dc0d723 (diff)
Added by Eric Helms 3 months ago

Fixes #31662: Set enable_http to ensure pub dir is deployed to Pulp vhost

History

#1 Updated by The Foreman Bot 3 months ago

  • Assignee set to Eric Helms
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-foreman_proxy_content/pull/315 added

#2 Updated by Tomer Brisker 3 months ago

  • Target version set to 2.3.3

#3 Updated by The Foreman Bot 3 months ago

  • Fixed in Releases 2.4.0 added

#4 Updated by Eric Helms 3 months ago

  • Status changed from Ready For Testing to Closed

#5 Updated by Amit Upadhye about 1 month ago

  • Category set to Foreman modules

Also available in: Atom PDF