Katello/Foreman PXE boot files

Problem:

I am starting with provisioning of servers via PXE boot from foreman/katello using the synced content. I have got it working with the predefined external installation medias from mirror.centos.org. However, I want to use the synced content and I can set everything up, however, the boot kernel and initrd in tftp are empty:

# ls -la /var/lib/tftpboot/boot/
total 141648
drwxr-xr-x. 2 foreman-proxy root              4096 Jan 15 09:12 .
drwxr-xr-x. 8 root          root               177 May 12  2020 ..
-rw-r--r--. 1 foreman-proxy foreman-proxy        0 Jan 15 07:54 centos-7-base-30554-initrd.img
-rw-r--r--. 1 foreman-proxy foreman-proxy        0 Jan 15 07:54 centos-7-base-30554-vmlinuz
-rw-r--r--. 1 foreman-proxy foreman-proxy        0 Jan 15 09:12 centos-8-base-30724-initrd.img
-rw-r--r--. 1 foreman-proxy foreman-proxy        0 Jan 15 09:12 centos-8-base-30724-vmlinuz
-rw-r--r--. 1 foreman-proxy foreman-proxy 73623376 Nov 18 21:59 centos-8-mirror-vhXw3RnU7BDi-initrd.img
-rw-r--r--. 1 foreman-proxy foreman-proxy  9514120 Sep 25 21:57 centos-8-mirror-vhXw3RnU7BDi-vmlinuz
-rw-r--r--. 1 foreman-proxy foreman-proxy 55129656 Oct 26 17:25 centos-mirror-v21mbm04pSQW-initrd.img
-rw-r--r--. 1 foreman-proxy foreman-proxy  6769256 Oct 19 18:23 centos-mirror-v21mbm04pSQW-vmlinuz

Obviously, booting centos-8-base-30724-vmlinuz won’t work. How do I fix this?

Foreman and Proxy versions:
Katello 3.18.1, Foreman 2.3.1

Distribution and version:
CentOS 7.9.2009

O.K. I have found this in /var/log/foreman-proxy/proxy.log:

2021-01-15T09:12:39 b930d3c4 [I] [19789] Started task ["/usr/bin/wget", "--connect-timeout=10", "--dns-timeout=10", "--read-timeout=60", "--tries=3", "--no-check-certificate", "-nv", "-c", "http://foreman-proxy.example.com/pulp/repos/ORG/Testing/centos8/custom/centos8/BaseOS_x86_64//images/pxeboot/vmlinuz", "-O", "/var/lib/tftpboot/boot/centos-8-base-30724-vmlinuz"]

However, since the upgrade from katello 3.17.2 to 3.18.1 the content proxy doesn’t listen to port 80 anymore.

Was there any infra changes lately @ehelms @ekohl ?

Well it seems, the content proxy should still listen to port 80 but doesn’t because of some changes and a bug, unless puppet content is enabled on the proxy.

See thread https://community.theforeman.org/t/content-proxy-not-listing-to-port-80-anymore and issue Bug #31662: Foreman content proxy doesn't listen on port 80 anymore - Installer - Foreman