COS-3946: Backport rhel-10.2 support to release-4.21 branch#1898
COS-3946: Backport rhel-10.2 support to release-4.21 branch#1898prestist wants to merge 5 commits intoopenshift:release-4.21from
Conversation
openshift-ci
bot
added
the
approved
prestist
force-pushed
the
release-4.21
branch
from
7cf9867 to
da40fa0
Compare
prestist
changed the title
prestist
force-pushed
the
release-4.21
branch
from
da40fa0 to
f135dcd
Compare
Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
- Let's sync the CI with what we have also in rhel-coreos-config, doing it for both RHEL 9/10 Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
prestist
force-pushed
the
release-4.21
branch
from
f135dcd to
a229d48
Compare
|
probably also need to backport 2ba2ed9 |
|
Once we merge #1899 I will backport it here as well. Ok I will include that. |
- Fix wrong versions of repos under rhel-10.2 Signed-off-by: Renata Ravanelli <rravanel@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: marmijo, prestist 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 |
cverna
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@prestist: This pull request references COS-3946 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.z" version, but no target version was set. 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. |
|
/label backport-risk-assessed |
|
/retest |
|
@cverna: The label(s) 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. |
|
New changes are detected. LGTM label has been removed. |
|
Ok, brought in the change that landed in master now as well. |
Make curl failures non-fatal so builds can continue with whatever repos are available. This allows the script to work now with just rhel96 repos while automatically working when the rhel102 service gets provisioned.
|
@prestist: 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. |
| rm -f "$dest" | ||
| for url in "${urls[@]}"; do | ||
| curl --fail -L "$url" >> "$dest" | ||
| curl --fail -L "$url" >> "$dest" || echo "Warning: Failed to fetch $url" >&2 |
There was a problem hiding this comment.
I'm concerned this change might obscure infra issues with RHEL 9.6 repos. We'd want the script to fail fast if those repos are unavailable for any reason.
Are we also hitting this issue on the master branch and does this need to be changed there too?
6 participants
Backport rhel-10.2 support to release-4.21 branch from master (PR #1892) and enable rhel-10.2 plashets.