smart proxy registers prior to pulpcore being available
I'm not sure what has changed, but it seems that the smart proxy registration is now happening before pulpcore is fully up and serving its capabilities. This results in katello preferring pulp2 for file/docker content instead of pulp3.
After install you can see in the foreman proxy logs:
2020-04-21T20:56:38 131ba2fb [E] Could not fetch capabilities: 765: unexpected token at '<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<title>503 Service Unavailable</title>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
Refreshing the smart proxy after install causes the problem to correct itself. You can check this on the console too:
SmartProxyFeature.joins(:feature).where("features.name" => "Pulpcore")
The capabilities will be blank
This is the cause of the current pipeline failure: https://ci.centos.org/job/foreman-katello-nightly-test/828/tapResults/
The foreman proxy w/content can't sync because the repository was created in pulp2, but is being served from pulp3 via apache.
#2 Updated by Ewoud Kohl van Wijngaarden 11 months ago
- Triaged changed from No to Yes
- Target version set to 2.0.1
- Category set to Foreman modules
This was never guaranteed by the installer. If it worked in the past, it happened to work by chance. This sounds like a good candidate to cherry pick into 2.0.
#5 Updated by Ewoud Kohl van Wijngaarden 10 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman_proxy_content|34aa29ab3acd98b4fc403c0c778e0c67f7d9b53c.