Example PR: https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_console-operator/229/pull-ci-openshift-console-operator-master-e2e-aws-upgrade/100#openshift-tests-disruptive-cluster-upgrade-should-maintain-a-functioning-cluster-featureclusterupgrade-suiteopenshift-serial The message: ``` Cluster did not complete upgrade: timed out waiting for the condition ``` In: ``` fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:138]: during upgrade Unexpected error: <*errors.errorString | 0xc002137310>: { s: "Cluster did not complete upgrade: timed out waiting for the condition", } Cluster did not complete upgrade: timed out waiting for the condition occurred ``` Could likely be clearer to help diagnose what happened to fail the upgrade.
The team has some ideas to improve the error output here (like printing the ClusterVersion status). The general process here should be to look at the stdout/stderr and look for ClusterVersion transitions. The cvo logs would be another place to look.
Probably affects 4.1 too, but so far has only been reported in origin/master (~4.2) builds. We can move Version back to 4.1 if/when we see it there.
Since this is related to CI and the fix landed in master we're just going to close this. No need for QE verification.