Bug #29589: smart proxy registers prior to pulpcore being available - Installer - Foreman

Actions

Copy link

Bug #29589

closed

smart proxy registers prior to pulpcore being available

Added by Justin Sherrill about 4 years ago. Updated almost 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ewoud Kohl van Wijngaarden

Category:

Foreman modules

Target version:

Foreman - 2.0.1

Difficulty:

Triaged:

Yes

Bugzilla link:

Pull request:

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

Fixed in Releases:

Foreman - 2.0.1, Foreman - 2.1.0

Found in Releases:

Red Hat JIRA:

Description

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">
<html><head>
<title>503 Service Unavailable</title>
</head><body>
<h1>Service Unavailable</h1>
<p>The server is temporarily unable to service your
request due to maintenance downtime or capacity
problems. Please try again later.</p>
</body></html>
'

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.

Actions

Copy link

Updated by Justin Sherrill about 4 years ago

Subject changed from smart proxy registers prior to pulp being available to smart proxy registers prior to pulpcore being available

Actions

Copy link

Updated by Ewoud Kohl van Wijngaarden about 4 years ago

Category set to Foreman modules
Target version set to 2.0.1
Triaged changed from No to Yes

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.

Actions

Copy link

Updated by The Foreman Bot about 4 years ago

Status changed from New to Ready For Testing
Assignee set to Ewoud Kohl van Wijngaarden
Pull request https://github.com/theforeman/puppet-foreman_proxy_content/pull/252 added