[6.16.z] Add a test case for metadata repair on capsule complete sync (#16835)

[vsedmik]

Problem Statement

Fix for the issue linked bellow has been backported to 6.16.1. We already have test coverage for this in stream and could have the same in 6.16.z.

Solution

git cherry-pick <id> && git push 6.16.z

Related Issues

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

PRT test Cases example

trigger: test-robottelo
pytest: tests/foreman/api/test_capsulecontent.py -k test_complete_sync_fixes_metadata

[vsedmik]

trigger: test-robottelo
pytest: tests/foreman/api/test_capsulecontent.py -k test_complete_sync_fixes_metadata

[Satellite-QE]

PRT Result

Build Number: 9600
Build Status: UNSTABLE
PRT Comment: pytest tests/foreman/api/test_capsulecontent.py -k test_complete_sync_fixes_metadata --external-logging
Test Result : ===== 1 passed, 25 deselected, 39 warnings, 1 error in 2264.29s (0:37:44) ======

[vsedmik]

^ checkin failed at AAP at teardown. Unrelated but rerunning...

[Satellite-QE]

PRT Result

Build Number: 9601
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/api/test_capsulecontent.py -k test_complete_sync_fixes_metadata --external-logging
Test Result : ========== 1 passed, 25 deselected, 39 warnings in 1776.68s (0:29:36) ==========

[pondrejk]

@vsedmik non blocking question, shouldn't this be checked also with some RH repo?

[vsedmik]

@vsedmik non blocking question, shouldn't this be checked also with some RH repo?

@pondrejk in this case the root cause was in the way how the complete sync was (or actually was not) triggered. It is independent from "what actual metadata" are repaired.
On the other hand I could imagine hardening this test case a bit with wider metadata set being fixed/tested, for example kickstart-specific content like treeinfo etc. But such an update would probably need to come through the master branch first (this is only cherry-pick). Anyway thank you for the tip, I have put it on my improvements list.