release-controller: update RHEL 10.1 repo urls

[dustymabe]

Since 10.1 isn't an EUS release we have to use different URLs here.

[travier]

Ah, might be the same for nfs & ha repos

[dustymabe]

Ah, might be the same for nfs & ha repos

Yes, you are right. I checked. Updated.

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@dustymabe: no rehearsable tests are affected by this change

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[travier]

/lgtm

[dustymabe]

/assign bradmwilliams

[dustymabe]

/assign bradmwilliams

oh nice. didn't know I could do that.

[bradmwilliams]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bradmwilliams, dustymabe, travier

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• core-services/release-controller/OWNERS [bradmwilliams]

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

[openshift-ci]

@dustymabe: 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-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci]

@dustymabe: Updated the following 14 configmaps:

• base-repos configmap in namespace ocp at cluster build07 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster build09 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster build11 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster core-ci using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster vsphere02 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster build01 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster build02 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster build04 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster build05 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster app.ci using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster build03 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster build06 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster build08 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo
• base-repos configmap in namespace ocp at cluster build10 using the following files:
  • key ocp-4.22-rhel101.repo using file core-services/release-controller/_repos/ocp-4.22-rhel101.repo

Details

In response to this:

Since 10.1 isn't an EUS release we have to use different URLs here.

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-sigs/prow repository.