Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2027815 - Executing remove-pulp2 after a successful Satellite 6.10 upgrade breaks synchronizations and repositories.
Summary: Executing remove-pulp2 after a successful Satellite 6.10 upgrade breaks synch...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.10.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: 6.10.2
Assignee: satellite6-bugs
QA Contact: Gaurav Talreja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-30 18:32 UTC by James Jeffers
Modified: 2024-12-20 21:40 UTC (History)
13 users (show)

Fixed In Version: rubygem-foreman_maintain-0.8.22-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2025049
Environment:
Last Closed: 2022-01-19 14:25:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34045 0 High Closed Executing remove-pulp2 after a successful Satellite 6.10 upgrade breaks synchronizations and repositories. 2021-12-08 17:10:50 UTC
Red Hat Knowledge Base (Solution) 6532721 0 None None None 2021-11-30 18:32:20 UTC
Red Hat Product Errata RHBA-2022:0189 0 None None None 2022-01-19 14:25:45 UTC

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
Note You need to log in before you can comment on or make changes to this bug.