Bug 2027815

Summary: Executing remove-pulp2 after a successful Satellite 6.10 upgrade breaks synchronizations and repositories.
Product: Red Hat Satellite Reporter: James Jeffers <jjeffers>
Component: Satellite MaintainAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Gaurav Talreja <gtalreja>
Severity: high Docs Contact:
Priority: high    
Version: 6.10.0CC: ahumbe, apatel, aupadhye, jkrajice, jsherril, kgaikwad, ldelouw, mkalyat, msunil, osousa, pdwyer, sadas, saydas
Target Milestone: 6.10.2Keywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-foreman_maintain-0.8.22-2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2025049 Environment:
Last Closed: 2022-01-19 14:25:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Gaurav Talreja 2021-12-28 14:27:36 UTC 
Verified.

Tested on Satellite 6.10.2 Snap 2.0
Version: rubygem-foreman_maintain-0.8.22-2.el7sat.noarch

Steps:
1. Sync a few custom repos with a few CDN repos, create and publish ContentView.
2. Migrate contents from Pulp2to3 and perform a Satellite upgrade to 6.10.
3. # satellite-maintain content remove-pulp2
4. Sync repos again after remove-pulp2

Observations:
remove-pulp2 now restarts pulpcore services after pulp2 data removal, which solves the issue of syncing repos post-upgrade.
Comment 6 errata-xmlrpc 2022-01-19 14:25:42 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 Maintenance 6.10.2 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-2022:0189