OCPBUGS-56805: fix: patch status instead of updating it to avoid failed loop#306
OCPBUGS-56805: fix: patch status instead of updating it to avoid failed loop#306damdo wants to merge 1 commit intoopenshift:mainfrom
Conversation
|
@damdo: This pull request references Jira Issue OCPBUGS-56805, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed 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 |
|
/cherry-pick release-4.19 |
|
@damdo: once the present PR merges, I will cherry-pick it on top of 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. |
|
/test unit |
|
/hold I think this needs some tweaking as we are not computing the patchBase on all the changes but only on the conditions diff. |
|
@damdo: The following tests failed, say
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. |
|
Superseded by #331 |
|
@damdo: This pull request references Jira Issue OCPBUGS-56805. The bug has been updated to no longer refer to the pull request using the external bug tracker. 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. |
At the moment the
cluster-capi-operatormanager is running in a hot loop trying to Update() the ClusterOperator status with the most recent conditions.(more logs here)
This should instead be using a Patch() to do so to avoid conflicts on all the non relevant fields.
This is a short term fix until we reintroduce a more refined status updating mechanism + SSA which was originally merged with: #256 but got reverted by #273