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 1989282 - In satellite upgrade, content switchover failed with status 1
Summary: In satellite upgrade, content switchover failed with status 1
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.10.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.10.0
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-02 20:15 UTC by Devendra Singh
Modified: 2021-08-11 11:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-11 11:53:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Devendra Singh 2021-08-02 20:15:40 UTC 
Description of problem: In satellite upgrade, content switchover failed with status 1


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

How reproducible:
1/1 (DB upgrade)

Steps to Reproduce:
1. Restore satellite 6.9 using specific customer database backup.
2. Run the pulp migration
3. Pulp migration partially completed successfully.
4. Approved the corrupted content to unblock the upgrade execution.
5. Run the upgrade from 6.9.z to 6.10 Snap11.

foreman-maintain upgrade run --whitelist="disk-performance" --target-version 6.10 -y
Checking for new version of satellite-maintain..
Nothing to update, can't find new version of satellite-maintain.
Running preparation steps required to run the next scenarios
.............
.............
Running Procedures before migrating to Satellite 6.10
...........
...........
Switch support for certain content from Pulp 2 to Pulp 3: 
2021-08-02 15:33:52 -0400: Importing migrated content type package_group: 40500/45506
Content Migration completed successfully
Performing a check to verify everything that is needed has been migrated
Switching specified content over to pulp 3                            [31m[1m[FAIL][0m
Failed executing foreman-rake katello:pulp3_content_switchover, exit status 1:
ERROR: at least one Erratum record has migrated_pulp3_href NULL value
Checking for valid Katello configuraton.
--------------------------------------------------------------------------------
Scenario [Migration scripts to Satellite 6.10] failed

The following steps ended up in failing state:
[content-switchover]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="content-switchover"



Actual results:
Satellite upgrade failed.

Expected results:
Satellite upgrade should be completed successfully.

Additional info:
Comment 9 Justin Sherrill 2021-08-04 17:24:52 UTC 
I'm tempted to close this as NOTABUG, as it looks like the database is clearly corrupt and missing information.  Do you agree?  

We'd be happy to look at the database pre-migration to confirm that state if you can set it up.
Thanks!
Note You need to log in before you can comment on or make changes to this bug.