Description of problem:

[Regression] The "hammer content-view version republish-repositories" action is not republishing repository metadata for the content-view versions in Satellite 6.14

Till 6.13, When using that command with "--force true", It will generate two types of actions within the task:

Actions::Katello::ContentViewVersion::RepublishRepositories
Actions::BulkAction ( for Actions::Katello::Repository::MetadataGenerate ) for individual repos in the CV version.

Starting from 6.14, I don't see that BulkAction task anymore and the main "Actions::Katello::ContentViewVersion::RepublishRepositories" task completes in seconds.

This effectively makes "5.17. Republishing Content View Metadata" completely useless when CV\CCV has RHEL repos

This is problematic in the following situations where

• A backup without pulp was restored and CU cannot afford to perform a new version Publish for CV ( to not include any new content )

• For some reason, the repodata was corrupted\found missing from the filesystem from within the CV versions

• [Maybe] Disconnected satellites , where after content import, repos might be showing less count of packages ( from CVs ) and a CV metadata republish is needed.

And the only way to fix it is by performing a new CV version Publish.

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

satellite-6.14.0-3.el8sat.noarch
foreman-3.7.0.2-1.el8sat.noarch
katello-4.9.0-1.el8sat.noarch

How reproducible:

Always

Steps to Reproduce:
1. Install a Satellite 6.14 and Sync one RHEL repo
2. Add the repo to a CV and publish a new version
3. Register a system and associate it with that CV and Library env
4. Perform yum repolist to verify the repo is visible and accessible from the client end
5. On Satellite "rm -rf /var/lib/pulp/media/artifact/*"
6. Repeat Step 4
7. On Satellite:
--> Complete Sync the repo
--> Verify Content Checksum the repo
--> Use hammer to republish the content-view version metadata forcefully

8. Repeat Step 4
9. Publish an entirely new version of the CV
10. Repeat Step 4

Actual results:

Step 6: 500\502 errors by yum as repomd.xml related artifact is missing from satellite
Step 8. Same scenario
Step 10: Issue fixed

Expected results:

On Step 7 only, the issue should be fixed.

Additional info:

It very well could be a regression due to https://bugzilla.redhat.com/show_bug.cgi?id=2184278