Foreman » Installer

Description of problem:

The pulp team has indicated smart proxy sync with python repositories is expected to use/pypiover /pulp/content since the latter is only around for legacy publication sync. We will need to modify the Apache config to allow /pypi requests. This will need a puppet-pulpcore change and container-ctl to build this into the foreman installer (and probably an upgrade job to fix this).

This change was used to great effect on a dev environment:

<Location "/pypi">
RequestHeader unset X-CLIENT-CERT
RequestHeader set X-CLIENT-CERT "%{SSL_CLIENT_CERT}s" env=SSL_CLIENT_CERT
RequestHeader set X-FORWARDED-PROTO expr=%{REQUEST_SCHEME}
ProxyPass unix:///run/pulpcore-api.sock|http://pulpcore-api/pypi timeout=600
ProxyPassReverse unix:///run/pulpcore-api.sock|http://pulpcore-api/pypi
</Location>
How reproducible:

Always

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

Run curl k -s <https://$(hostname)/pypi/&lt;org&gt;><environment>-<repo_label>/simple/

Actual behavior:
404 Not Found

Expected behavior:
The /pypi endpoint should connect to pulp’s pypi endpoint.