HTTPS Error 502 - Bad Gateway on Clients, pulpcore-content: FileNotFoundError on Server after Enabling Puppet


We are trying to enable puppet on our forman/katello installation. After following the steps outlined in section 1.3 of the Configuring Hosts Using Puppet guide, yum updates on clients fail with an HTTP error 502. On the foreman server, I can see errors in var log messages from pulpcore-content about files not found, and indeed if I browse to the path, directories are missing.

Expected outcome:

Enabling puppet on foreman should not break yum for clients

Foreman and Proxy versions:


Foreman and Proxy plugin versions:
Katello 4.2.2
Puppet 1.0.5
Distribution and version:

Other relevant data:
/var/log/messages on server:
pulpcore-content: FileNotFoundError: [Errno 2] No such file or directory: ‘/var/lib/pulp/media/artifact/8b/45b07b03813d3248c4fe4f407c4d9e4ebe91ca63591cc9e13243ec719c69e8’

when running yum update on client:
https://URL/repomd.xml: [Errno 14] HTTPS Error 502 - Bad Gateway