MCO-1481: blocked-edges/4.18.0-rc.*-MachineConfigServerCARotation: Declare new risk#6463
Conversation
|
@wking: This pull request references MCO-1481 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.19.0" 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. |
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
Bot
added
the
approved
wking
force-pushed
the
MachineConfigServerCARotation
branch
from
1c92d4a to
5050846
Compare
|
Quay 502 is unrelated. /test e2e |
…risk We don't have to declare this for updated into 4.19, because 4.19 was born with rc.0 as it's update floor: $ git blame --first-parent build-suggestions/4.19.yaml | head -n2 11cc1f7 (openshift-merge-bot[bot] 2024-12-05 18:28:06 +0000 1) default: 11cc1f7 (openshift-merge-bot[bot] 2024-12-05 18:28:06 +0000 2) minor_min: 4.18.0-rc.0 so ec.4 cannot update directly to any 4.19 releases.
wking
force-pushed
the
MachineConfigServerCARotation
branch
from
5050846 to
53dc081
Compare
| to: 4.18.0-rc.2 | ||
| from: 4[.]18[.]0-ec[.]4[+].* |
There was a problem hiding this comment.
Do I understand correctly that we will declare the risk as fixed after z_min in build-suggestions/4.18.yaml is bumped to a version higher than 4.18.0-ec.4 and there are no new upgrade paths from 4.18.0-ec.4, correct?
There was a problem hiding this comment.
Yup, we'll declare it fixed by 4.18.1, because at GA-time, we raise that z_min to the GA release.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DavidHurta, wking 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 |
3 participants
No description provided.