Bug 1946360

Summary:	Pulp3 services won't start after running a migration after performing switchover
Product:	Red Hat Satellite	Reporter:	Lai <ltran>
Component:	Repositories	Assignee:	James Jeffers <jjeffers>
Status:	CLOSED ERRATA	QA Contact:	Tasos Papaioannou <tpapaioa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	egolov, jsherril
Target Milestone:	6.9.1	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-3.18.1.27-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-26 17:36:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lai 2021-04-05 21:10:25 UTC

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

Comment 1 Justin Sherrill 2021-04-06 14:11:29 UTC

Created redmine issue https://projects.theforeman.org/issues/32256 from this bug

Comment 3 Tasos Papaioannou 2021-04-16 17:21:07 UTC

Verified on 6.9.1 snap 2.0.

Comment 8 errata-xmlrpc 2021-04-26 17:36:58 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Satellite 6.9.1 Async Bug Fix Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1371