Description of problem: Recently created repository leads to corrupted migrated remote. (Pulp2 to Pulp3 switch) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create sync and publish a repository 2. migrate from Pulp 2 to Pulp 3 3. Actual results: An error is raised: undefined method `pulp3_remote_href' for nil:NilClass (NoMethodError) Expected results: Additional info:
Created redmine issue https://projects.theforeman.org/issues/33150 from this bug
Verified. Tested on Satellite 6.9.6 Snap 2.0 Steps: 1. Create 1-2 large repos/sync RH repos like rhel-server-rhscl-7-rpms and put that repos in a content view. 2. Publish the content view and immediately start the Pulp 2 -> 3 migration with, # satellite-maintain content prepare 3. Watch production logs for messages/warnings to run the migration again. Observations: Repositories belonging to that CV with ID/name unmigrated due to being created during the Pulp 3 migration. And following logs are seen in production logs after the migration completes, 2021-09-17T07:57:43 [W|app|] Library repository with ID 1 and name Red Hat Ansible Engine 2.9 RPMs for Red Hat Enterprise Linux 7 Server x86_64 unmigrated due to being associated with an actively-publishing content view. The migration will need to be run again. 2021-09-17T07:57:43 [W|app|] Repositories belonging to Content View with ID 2 and name test_cv unmigrated due to being created during the Pulp 3 migration. The migration will need to be run again. 2021-09-17T07:57:43 [W|app|] Library repository with ID 2 and name Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server x86_64 7Server unmigrated due to being associated with an actively-publishing content view. The migration will need to be run again. 2021-09-17T07:57:43 [W|app|] Repositories belonging to Content View with ID 2 and name test_cv unmigrated due to being created during the Pulp 3 migration. The migration will need to be run again. Thanks, Ian Ballou for helping with the detailed steps. While discussing with him, we noticed when the migration plan is empty, all repositories get migrated and CV's repositories receive version_hrefs if there is no error during the migration, so raised another BZ[1] to track this issue. [1] https://bugzilla.redhat.com/show_bug.cgi?id=2005392
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 6.9.6 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-2021:3628