-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: SDN-5377: blocked-edges/4.14.*-OVNTransitSwitchSubset: Declare 4.13-to-4.14 risk #6081
base: master
Are you sure you want to change the base?
Conversation
…4 risk The risk is briefly covered in the linked release note since 2024-09-18 [1]. I'm setting autoExtend, because unless some future 4.13.z addresses this (unlikely, with 4.13.z going end-of-life on 2014-11-27 [2]), or a future 4.14.z addresses this, we'll likely have to continue to carry it forward to every 4.13-to-4.14 update we ever support. This will make life more difficult for customers who traditionally wait until there's an update we recommend unconditionally. All OVN cluster administrators on 4.13 will need to read through the risk message and linked docs, and decide for themselves whether they are comfortable accepting the risk and updating to 4.14. Generated by writing the 4.14.0 risk by hand, and then copying out to all existing 4.14.z update targets with: $ curl -s 'https://api.openshift.com/api/upgrades_info/graph?channel=candidate-4.14&arch=amd64' | jq -r '.nodes[] | .version' | grep '^4[.]14[.][0-9]*$' | grep -v 4.14.0 | while read VERSION; do sed "s/4.14.0/${VERSION}/" blocked-edges/4.14.0-OVNTransitSwitchSubset.yaml > "blocked-edges/${VERSION}-OVNTransitSwitchSubset.yaml"; done [1]: openshift/openshift-docs#81666 (comment) [2]: https://access.redhat.com/support/policy/updates/openshift#dates
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wking The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@wking: This pull request references SDN-5377 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 spike to target the "4.18.0" version, but no target version was set. In 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. |
@wking: all tests passed! Full PR test history. Your PR dashboard. 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. |
The risk is briefly covered in the linked release note since 2024-09-18.
I'm setting
autoExtend
, because unless some future 4.13.z addresses this (unlikely, with 4.13.z going end-of-life on 2014-11-27), or a future 4.14.z addresses this, we'll likely have to continue to carry it forward to every 4.13-to-4.14 update we ever support. This will make life more difficult for customers who traditionally wait until there's an update we recommend unconditionally. All OVN cluster administrators on 4.13 will need to read through the risk message and linked docs, and decide for themselves whether they are comfortable accepting the risk and updating to 4.14.Generated by writing the 4.14.0 risk by hand, and then copying out to all existing 4.14.z update targets with:
$ curl -s 'https://api.openshift.com/api/upgrades_info/graph?channel=candidate-4.14&arch=amd64' | jq -r '.nodes[] | .version' | grep '^4[.]14[.][0-9]*$' | grep -v 4.14.0 | while read VERSION; do sed "s/4.14.0/${VERSION}/" blocked-edges/4.14.0-OVNTransitSwitchSubset.yaml > "blocked-edges/${VERSION}-OVNTransitSwitchSubset.yaml"; done