🐛 ROSA: Fix version gate Ack for rosa hcp y-stream version upgrade#5166
🐛 ROSA: Fix version gate Ack for rosa hcp y-stream version upgrade#5166k8s-ci-robot merged 1 commit intokubernetes-sigs:mainfrom
Conversation
|
Hi @serngawy. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
/ok-to-test |
|
/hold |
|
/unhold |
|
@serngawy could you please add a Release Note in the description of the PR for this one? Thanks! |
|
Can you confirm that we are introducing the user flow that we will always require an Acknowledgement, (unless AlwaysAcknowledge) is set, for all Y-Stream upgrades (that's what the code flow looks like to me. This is being done even though OCP may NOT require it. OCP 4.16 to 4.17 does not require an acknowledge. @serngawy can you confirm this is also ROSA-HCP's use case, or are they aware of when to require the acknowledgement? |
jnpacker
left a comment
There was a problem hiding this comment.
Fix message, and question on whether this flow is now forced for all Y stream upgrades.
The code check first if there is an versionGate Acknowledge is required, if upgrading y-stream doesn't require Acknowledge the upgrade will proceed similar to z-stream upgrade. The workflow is; |
jnpacker
left a comment
There was a problem hiding this comment.
Got an explanation and a look at the code as to why ACK doesn't apply when not required.
Signed-off-by: melserngawy <melserng@redhat.com>
|
lgtm |
|
@nrb @richardcase any of you able to do an approver type review? TY |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nrb 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 |
|
CI's fixed. /unhold |
|
/test pull-cluster-api-provider-aws-test Failed due to CI account limits, not this code. |
What type of PR is this?
Bug
What this PR does / why we need it:
This PR approve the gate version acknowledgment for ROSA-HCP y-stream upgrade
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist:
Release note: