6.14.z-fix keyError: 'rhel8 + _bos' from api>tests_repository.py

[vijaysawant]

Problem Statement

During TFA, found test test_positive_sync_kickstart_check_os was failing due to error below
KeyError: 'rhel8 + "_bos"' and KeyError: 'rhel9 + "_bos"'

Solution

Along with small change in failed test, make changes in robottelo constants keys for REPOSET>kickstart>distro from
rhel8 to rhel8_bos
rhel9 to rhel9_bos

Related Issues

N/A

PRT test Cases example

trigger: test-robottelo
pytest: tests/foreman/api/test_repository.py -k 'test_positive_sync_kickstart_check_os'

trigger: test-robottelo
pytest: tests/foreman/cli/test_repositories.py -k 'test_positive_disable_rh_repo_with_basearch'

[vijaysawant]

trigger: test-robottelo
pytest: tests/foreman/api/test_repository.py -k 'test_positive_sync_kickstart_check_os'

[Satellite-QE]

PRT Result

Build Number: 6669
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/api/test_repository.py -k test_positive_sync_kickstart_check_os --external-logging
Test Result : ========= 4 passed, 165 deselected, 250 warnings in 1021.33s (0:17:01) =========

[vijaysawant]

trigger: test-robottelo
pytest: tests/foreman/cli/test_repositories.py -k 'test_positive_disable_rh_repo_with_basearch'

[Satellite-QE]

PRT Result

Build Number: 6672
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/cli/test_repositories.py -k test_positive_disable_rh_repo_with_basearch --external-logging
Test Result : =========== 1 passed, 4 deselected, 13 warnings in 803.11s (0:13:23) ===========

[vsedmik]

In master this was changed by #14673. But I can't see the changes in 6.15.z.
Can you raise this against 6.15.z and CP back to 6.14.z to keep the branches consistent?

[vijaysawant]

In master this was changed by #14673. But I can't see the changes in 6.15.z. Can you raise this against 6.15.z and CP back to 6.14.z to keep the branches consistent?

This branch is locally checkout against upstream/6.14.z and I am thinking to open separate PR for 6.15.z

[vijaysawant]

In master this was changed by #14673. But I can't see the changes in 6.15.z. Can you raise this against 6.15.z and CP back to 6.14.z to keep the branches consistent?

This branch is locally checkout against upstream/6.14.z and I am thinking to open separate PR for 6.15.z

Here it is PR for 6.15.z #14878