-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
BU Product Work
-
False
-
None
-
False
These are alarming conditions which may frighten customers, and we don't want to see them in our own, controlled, repeatable update CI. This example job had logs like:
Feb 18 21:11:25.799 E clusteroperator/openshift-apiserver changed Degraded to True: APIServerDeployment_UnavailablePod: APIServerDeploymentDegraded: 1 of 3 requested instances are unavailable for apiserver.openshift-apiserver ()
And the job failed, but none of the failures were "something made openshift-apiserver mad enough to go Degraded".
Definition of done:
- Same as
OTA-362 - File bugs or the existing issues
- If bug exists then add the tests to the exception list.
- Unless tests are in exception list , they should fail if we see degraded != false.
- is blocked by
-
OTA-701 Communicate available and degraded condition definition to teams
-
- Closed
-
- is cloned by
-
TRT-1576 CI: fail update suite if any ClusterOperator go Available=False outside of updates
-
- Closed
-
- relates to
-
OTA-362 CI: fail update suite if any ClusterOperator go Available=False
-
- Closed
-
- links to
(2 links to)