release-controller: Remove advanced-virt repo

[etrunko]

From RHEL 8.6 onwards there is no advanced virtualization repository
anymore.

Signed-off-by: Eduardo Lima (Etrunko) etrunko@redhat.com

[openshift-ci]

Hi @etrunko. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[miabbott]

/ok-to-test
/approve

[HuijingHei]

@etrunko there is new file core-services/release-controller/_repos/ocp-4.11-rhel86.repo refer to #27333, could you help to remove advanced-virt repo in core-services/release-controller/_repos/ocp-4.11-rhel86.repo, thanks!

[etrunko]

@etrunko there is new file core-services/release-controller/_repos/ocp-4.11-rhel86.repo refer to #27333, could you help to remove advanced-virt repo in core-services/release-controller/_repos/ocp-4.11-rhel86.repo, thanks!

Should I revert the changes on ocp-4.11.rhel85.repo?

[HuijingHei]

@etrunko there is new file core-services/release-controller/_repos/ocp-4.11-rhel86.repo refer to #27333, could you help to remove advanced-virt repo in core-services/release-controller/_repos/ocp-4.11-rhel86.repo, thanks!

Should I revert the changes on ocp-4.11.rhel85.repo?

I think no need, ocp-4.11.rhel85.repo will be removed when move to rhel8.6, but not sure, need confirm from @miabbott

[miabbott]

I think no need, ocp-4.11.rhel85.repo will be removed when move to rhel8.6, but not sure, need confirm from @miabbott

Correct, we can leave the 8.5 repo definition as is; 8.6 is our future.

[etrunko]

I think no need, ocp-4.11.rhel85.repo will be removed when move to rhel8.6, but not sure, need confirm from @miabbott

Correct, we can leave the 8.5 repo definition as is; 8.6 is our future.

Okay then, I'm leaving it.

[etrunko]

Are we able to merge this one now?

[miabbott]

/lgtm
/assign @jupierce

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: etrunko, miabbott
To complete the pull request process, please assign smarterclayton after the PR has been reviewed.
You can assign the PR to them by writing /assign @smarterclayton in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• core-services/release-controller/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[etrunko]

Hi, is there anything pending with this MR?

[openshift-ci]

@etrunko: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[miabbott]

We still need approval from @jupierce or someone else in https://github.com/openshift/release/blob/master/core-services/release-controller/OWNERS

[travier]

I'm merging this one into #28521

[openshift-ci]

@etrunko: PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[travier]

/close

[openshift-ci]

@travier: Closed this PR.

Details

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.