Description of problem:
During the build02 update from 4.14.0-ec.1 to ec.2 I have noticed the following:
$ b02 get clusterversion version -o json | jq '.status.conditions[] | select (.type=="Failing")' { "lastTransitionTime": "2023-06-20T13:40:12Z", "message": "Multiple errors are preventing progress:\n* Cluster operator authentication is updating versions\n* Could not update customresourcedefinition \"alertingrules.monitoring.openshift.io\" (512 of 993): the object is invalid, possibly due to local cluster configuration", "reason": "MultipleErrors", "status": "True", "type": "Failing" }
There is a valid error (the Could not update customresourcedefinition... one) but the whole thing is cluttered by the "Cluster operator authentication is updating versions" message, which is imo not a legit reason for Failing=True condition and should not be there. Before I captured this one I saw the message with three operators instead of just one.
Version-Release number of selected component (if applicable):
4.14.0-ec.2
How reproducible:
No idea
- blocks
-
OCPBUGS-39558 "Cluster operator X is updating versions" is not a reason for Failing=True condition
- Closed
- is cloned by
-
OCPBUGS-39558 "Cluster operator X is updating versions" is not a reason for Failing=True condition
- Closed
- links to
-
RHEA-2024:6122 OpenShift Container Platform 4.18.z bug fix update