-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
False
-
False
-
NEW
-
NEW
-
Undefined
-
When CMO fails to reconcile, it sets the Available condition to false and Degraded to true. But there's no reason added for the Available condition which is confusing.
From https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-ovn-upgrade-4.6-stable-to-4.7-ci/1364216625124872192 in which CMO went degraded/unavailable:
"status": {
"conditions": [
{
"lastTransitionTime": "2021-02-23T17:37:04Z",
"message": "Rolling out the stack.",
"reason": "RollOutInProgress",
"status": "True",
"type": "Progressing"
},
{
"lastTransitionTime": "2021-02-23T16:16:13Z",
"message": "Failed to rollout the stack. Error: running task Updating Grafana failed: reconciling Grafana Deployment failed: updating Deployment object failed: waiting for DeploymentRollout of openshift-monitoring/grafana: got 1 unavailable replicas",
"reason": "UpdatingGrafanaFailed",
"status": "True",
"type": "Degraded"
},
{
"lastTransitionTime": "2021-02-23T17:37:04Z",
"message": "Rollout of the monitoring stack is in progress. Please wait until it finishes.",
"reason": "RollOutInProgress",
"status": "True",
"type": "Upgradeable"
},
{
"lastTransitionTime": "2021-02-23T16:01:41Z",
"status": "False",
"type": "Available"
}
]
The direct result in this case is that the e2e tests didn't surface the relevant information because they look at the Available reason first.