Bug #32256: Pulp3 services won't start after running a migration after performing switchover - Katello - Foreman

Actions

Copy link

Bug #32256

closed

Pulp3 services won't start after running a migration after performing switchover

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

Status:

Closed

Priority:

Normal

Assignee:

James Jeffers

Category:

Target version:

Katello 3.18.3

Difficulty:

Triaged:

Yes

Bugzilla link:

1946360

Pull request:

https://github.com/Katello/katello/pull/9283

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1946360

Description of problem:
After doing a switchover, a user can still run the migration command, but that also starts and ultimately stops pulp services so you can't enable or sync a repo.

Version-Release number of selected component (if applicable):
6.9.0

How reproducible:
100%

Steps to Reproduce:
1. Sync a repo
2. Perform migration until it's completed
3. Perform switchover until it's completed
4. Run migration command
5. Try to enable or sync a RH repo

Actual results:
"There was an issue with the backend service pulp3: 503 Service Unavailable"

Expected results:
Should sync or enable a repo successfully.

Additional info:
Work around is to start/enable the pulp workers:

systemctl start pulpcore-resource-manager pulpcore-api pulpcore-content pulpcore-worker@1 pulpcore-worker@2 pulpcore-worker@3 pulpcore-worker@4
systemctl enable pulpcore-resource-manager pulpcore-api pulpcore-content pulpcore-worker@1 pulpcore-worker@2 pulpcore-worker@3 pulpcore-worker@4