add PIT marker for repositories test

[vijaysawant]

Problem Statement

PIT marker missing for repositories component.

Solution

This PR changes

Related Issues

Proposing new default_rhel_version, changes made into the gitlab MR-1413

[ogajduse]

I am fine with the patch, but please remember that the test is fixed to use RHEL 9. That means when the client scenario is triggered by RHEL 10 compose being out, pytest will not pick this test due to the hard-code.

If you want to make any changes now, I would recommend using @pytest.mark.rhel_ver_list([settings.content_host.default_rhel_version]) to pin the test to exactly one RHEL version specified in the settings. It is currently RHEL 8, but that could eventually be changed to RHEL 9 if the team agrees. Feel free to propose a config change. In the PIT client automation pipeline, we are changing this constant to the RHEL version under test.

[vijaysawant]

I am fine with the patch, but please remember that the test is fixed to use RHEL 9. That means when the client scenario is triggered by RHEL 10 compose being out, pytest will not pick this test due to the hard-code.

If you want to make any changes now, I would recommend using @pytest.mark.rhel_ver_list([settings.content_host.default_rhel_version]) to pin the test to exactly one RHEL version specified in the settings. It is currently RHEL 8, but that could eventually be changed to RHEL 9 if the team agrees. Feel free to propose a config change. In the PIT client automation pipeline, we are changing this constant to the RHEL version under test.

In order to propose new value (default_rhel_version: 9) what other changes are require in the yaml file?
@ogajduse

[vijaysawant]

I am fine with the patch, but please remember that the test is fixed to use RHEL 9. That means when the client scenario is triggered by RHEL 10 compose being out, pytest will not pick this test due to the hard-code.
If you want to make any changes now, I would recommend using @pytest.mark.rhel_ver_list([settings.content_host.default_rhel_version]) to pin the test to exactly one RHEL version specified in the settings. It is currently RHEL 8, but that could eventually be changed to RHEL 9 if the team agrees. Feel free to propose a config change. In the PIT client automation pipeline, we are changing this constant to the RHEL version under test.

In order to propose new value (default_rhel_version: 9) what other changes are require in the yaml file? @ogajduse

I guess nothing apart from that rhel_major_version

[ogajduse]

Nothing apart from the default_rhel_version config needs to be changed.

Edit: Of course, assuming you use the setting in the rhel_ver_list marker.