Add a test case for metadata repair on capsule complete sync

[vsedmik]

Problem Statement

We are missing coverage for the customer case listed bellow

Solution

This PR proposes a test case to ensure that the complete capsule sync repairs the repository metadata.

Related Issues

https://issues.redhat.com/browse/SAT-28575

PRT test Cases example

Requires Katello/katello#11168

trigger: test-robottelo
pytest: tests/foreman/api/test_capsulecontent.py -k complete_sync_fixes_metadata
Katello:
  katello: 11168

[vsedmik]

trigger: test-robottelo
pytest: tests/foreman/api/test_capsulecontent.py -k complete_sync_fixes_metadata
Katello:
  katello: 11168

[Satellite-QE]

PRT Result

Build Number: 9198
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/api/test_capsulecontent.py -k complete_sync_fixes_metadata --external-logging
Test Result : ========== 1 passed, 25 deselected, 39 warnings in 2238.96s (0:37:18) ==========

[chris1984]

@vsedmik would a good 2nd test case after the repair and metadata have been verified to have a client that is connected to the capsule, try a yum repolist to verify it can pull down the metadata correctly? Or would that be to hard to mock out?

[vsedmik]

@vsedmik would a good 2nd test case after the repair and metadata have been verified to have a client that is connected to the capsule, try a yum repolist to verify it can pull down the metadata correctly? Or would that be to hard to mock out?

@chris1984 Actually we could extend this one to use the rhel_contenthost, register it via AK to the capsule and dnf repolist/update/install/whatever there. No mocking, just one extra VM used inside this test case. I was thinking if it's worth it and thought the assertion for restored artifacts would be enough. But if you think it's worth it we can do it.

[chris1984]

@vsedmik would a good 2nd test case after the repair and metadata have been verified to have a client that is connected to the capsule, try a yum repolist to verify it can pull down the metadata correctly? Or would that be to hard to mock out?

@chris1984 Actually we could extend this one to use the rhel_contenthost, register it via AK to the capsule and dnf repolist/update/install/whatever there. No mocking, just one extra VM used inside this test case. I was thinking if it's worth it and thought the assertion for restored artifacts would be enough. But if you think it's worth it we can do it.

That would be awesome if you could @vsedmik and it's not too much work.

[vsedmik]

trigger: test-robottelo
pytest: tests/foreman/api/test_capsulecontent.py -k complete_sync_fixes_metadata
Katello:
  katello: 11168

[Satellite-QE]

PRT Result

Build Number: 9248
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/api/test_capsulecontent.py -k complete_sync_fixes_metadata --external-logging
Test Result : ========== 1 passed, 25 deselected, 39 warnings in 2071.03s (0:34:31) ==========

[chris1984]

Looks great and thanks for updating the test @vsedmik