Bug #31662
Foreman content proxy doesn't listen on port 80 anymore
Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
Fixed in Releases:
Found in Releases:
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
History
#1
Updated by The Foreman Bot 6 months ago
Updated by - 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 6 months ago
Updated by - Target version set to 2.3.3
#3
Updated by The Foreman Bot 6 months ago
- Fixed in Releases 2.4.0 added
#4
Updated by Eric Helms 6 months ago
Updated by - Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman_proxy_content|2dc0d723e6e16e3094aa3bd2bffb083190fc2b30.
#5
Updated by Amit Upadhye 4 months ago
Updated by - Category set to Foreman modules
Fixes #31662: Set enable_http to ensure pub dir is deployed to Pulp vhost