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 1998223 - Pulp2 to Pulp3 Content switchover failed in the satellite upgrade
Summary: Pulp2 to Pulp3 Content switchover failed in the satellite upgrade
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.10.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.9.6
Assignee: Justin Sherrill
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-26 16:16 UTC by James Jeffers
Modified: 2021-12-01 08:56 UTC (History)
8 users (show)

Fixed In Version: rubygem-foreman_maintain-0.7.13
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1985165
Environment:
Last Closed: 2021-09-13 13:07:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 33149 0 None None None 2021-08-26 16:16:46 UTC

Comment 4 James Jeffers 2021-09-13 12:49:28 UTC
If the upgrade isn't part of 6.9.6, then perhaps we should close it for 6.9 z.

Comment 5 Justin Sherrill 2021-09-13 13:00:08 UTC
it is part of 6.9.6, but the fix is in foreman-maintain, and that will be delivered as part of 6.10

Comment 6 James Jeffers 2021-09-13 13:07:31 UTC
Ok, let's close this.


Note You need to log in before you can comment on or make changes to this bug.