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.

Description of problem:
Content migration fails for content where 'is_layered' configuration parameter is present.


Version-Release number of selected component (if applicable):
6.9.0 snap 12
python3-pulp-2to3-migration-0.6.0-1.el7pc.noarch
tfm-rubygem-pulp_2to3_migration_client-0.5.0-1.el7sat.noarch


How reproducible:
always


Steps to Reproduce:
1. on a blank SAT run satellite-installer --foreman-proxy-plugin-pulp-pulpcore-enabled true
2. add and sync a repo where is_layered parameter is present
3. run satellite-maintain prep-6.10-upgrade
4. run satellite-maintain content prepare


Actual results:
content migration fails


Expected results:
migration should succeed


Additional info:
patch available on https://patch-diff.githubusercontent.com/raw/pulp/pulp_rpm/pull/1936.patch

This likely has the same resolution as https://bugzilla.redhat.com/show_bug.cgi?id=1925799

Will leave it open as reproduction steps are different.

Pulp Redmine issue is MODIFIED. Moving state to post manually until our automation is fixed.

Verified on snap 19.1 with python3-pulp-rpm-3.9.0-1.el7pc.noarch

The migration and switchover succeeded.

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 (Moderate: Satellite 6.9 Release), 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/RHSA-2021:1313