NO-ISSUE: Add 4.15 rhocp repo to configure-vm.sh#3557
NO-ISSUE: Add 4.15 rhocp repo to configure-vm.sh#3557pacevedom wants to merge 3 commits intoopenshift:release-4.16from
Conversation
Manually add this repo to the configure-vm.sh script. The get_latest_rhocp_repo has been returning 4.15 and inadvertently enabling that repo until 4.16 went GA and the repo was publicly available. Now that this is the case, the scenario preparation for upgrade tests fails, as there is no repo configured to pull those packages. This PR fixes that by adding not just 4.16 repo, but also 4.15. This is a manual cherry-pick of openshift#3556
openshift-ci-robot
added
the
jira/valid-reference
|
@pacevedom: This pull request explicitly references no jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
Bot
added
the
approved
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: copejon, pacevedom The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test microshift-metal-tests |
|
/hold |
openshift-ci
Bot
added
the
do-not-merge/hold
|
New changes are detected. LGTM label has been removed. |
|
/test microshift-metal-tests |
pacevedom
force-pushed
the
repo-4.15
branch
3 times, most recently
from
5a7e959 to
b6af126
Compare
|
/hold cancel |
openshift-ci
Bot
removed
the
do-not-merge/hold
|
I believe this will conflict with: #3513 (in which the tests are passing so it should be fixing the issue present on |
|
/hold |
openshift-ci
Bot
added
the
do-not-merge/hold
|
@pacevedom: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/close |
|
@pacevedom: Closed this PR. DetailsIn response to this:
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. |
4 participants
Manually add this repo to the configure-vm.sh script. The get_latest_rhocp_repo has been returning 4.15 and inadvertently enabling that repo until 4.16 went GA and the repo was publicly available. Now that this is the case, the scenario preparation for upgrade tests fails, as there is no repo configured to pull those packages.
This PR fixes that by adding not just 4.16 repo, but also 4.15. This is a manual cherry-pick of #3556
Which issue(s) this PR addresses:
Closes #