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 1995694 - Upgrade re-run failed in the content migration stage.
Summary: Upgrade re-run failed in the content migration stage.
Keywords:
Status: CLOSED DUPLICATE of bug 1993844
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.10.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-19 15:48 UTC by Devendra Singh
Modified: 2021-08-19 18:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-19 18:35:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Devendra Singh 2021-08-19 15:48:08 UTC 
Description of problem: Upgrade re-run failed in the content migration stage.


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

How reproducible:
always

Steps to Reproduce:
1. Prepare the 6.9.z setup using the upgrade template.
2. Run the pre-migration steps before running the upgrade for 6.10 snap14.
3. Pulp migration completed successfully.
4  Run the upgrade, but it failed in the yum update with a package dependency issue.
5- Applied the workaround.
# yum remove -y rubygem-passenger
6- Rerun the upgrade but it failed in the content migration stage.

--------------------------------------------------------------------------------
Switch support for certain content from Pulp 2 to Pulp 3: 
Performing final content migration before switching content           [FAIL]
Failed executing foreman-rake katello:pulp3_migration, exit status 1:
 rake aborted!
The system appears to already be using pulp3 with all content migrated.
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.1.33/lib/katello/tasks/check_config.rake:15:in `block (2 levels) in <top (required)>'
/opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
Tasks: TOP => katello:pulp3_migration => katello:check_config
(See full trace by running task with --trace)
Checking for valid Katello configuraton.
--------------------------------------------------------------------------------
Scenario [Migration scripts to Satellite 6.10] failed.

The following steps ended up in failing state:

  [content-switchover]
  [packages-update]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="content-switchover,packages-update"


Actual results:
Upgrade failed in the content migration stage

Expected results:
Upgrade should be completed successfully.

Additional info:
Comment 1 Justin Sherrill 2021-08-19 18:35:34 UTC 
This is a 6.9 issue and

*** This bug has been marked as a duplicate of bug 1993844 ***
Note You need to log in before you can comment on or make changes to this bug.