Bug #31662: Foreman content proxy doesn't listen on port 80 anymore - Installer - Foreman

Actions

Copy link

Bug #31662

closed

Foreman content proxy doesn't listen on port 80 anymore

Added by Gerald Vogt over 3 years ago. Updated about 3 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Eric Helms

Category:

Foreman modules

Target version:

Foreman - 2.3.3

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/puppet-foreman_proxy_content/pull/315

Fixed in Releases:

Foreman - 2.4.0

Found in Releases:

Foreman - 2.3.1

Red Hat JIRA:

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

Actions

Copy link

Updated by The Foreman Bot about 3 years ago

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