If the migration plan is empty, all repositories get migrated.
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):
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.
The CV's repositories are migrated (have version_hrefs).
The CV's repositories are not migrated (nil version_hrefs).
Other related BZ that found this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1973245