Description of problem: With the BZ listed below, we are now filtering out repositories for the migration if they're being created or if they're related to a publishing content view. This means people can now migrate safely while doing these actions. However, in the very rare case that all repositories are excluded from the migration plan, this will actually tell Pulp to migrate all repositories. Version-Release number of selected component (if applicable): Satellite 6.9.0 How reproducible: Always, under the circumstances above. Steps to Reproduce: 1. Have a Satellite with one repository and put that repo in a content view 2. Publish the content view and immediately start the Pulp 2 -> 3 migration 3. If the timing is right, in the logs, you will see an empty migration plan. However, the CV's repositories will receive version_hrefs if there is no error during the migration. Actual results: The CV's repositories are migrated (have version_hrefs). Expected results: The CV's repositories are not migrated (nil version_hrefs). Additional info: Other related BZ that found this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1973245
Created redmine issue https://projects.theforeman.org/issues/34550 from this bug
Upstream bug assigned to jsherril
Moving to POST as upstream PR is merged.
Verified. Satellite 6.9.9-1.0 Synced large repos(rhscl, rhel7, extra, optional, baseos, appstream) and put that in CV. Just after `publishing`, ran `satellite-maintain content prepare`. Migration fails.
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 (Important: Satellite 6.9.9 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/RHSA-2022:1478