Description of problem: MCO reporting error during upgrade tests: Sep 11 12:18:24.201: INFO: Error running cluster/log-dump/log-dump.sh: fork/exec ../../cluster/log-dump/log-dump.sh: no such file or directory fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:139]: during upgrade Unexpected error: <*errors.errorString | 0xc0029880f0>: { s: "Pools did not complete upgrade: timed out waiting for the condition", } Pools did not complete upgrade: timed out waiting for the condition occurred Version-Release number of selected component (if applicable): https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/6930 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I0911 11:48:15.203575 19293 update.go:89] pod "etcd-quorum-guard-77fcc6f6f6-c89zq" removed (evicted) I0911 11:58:08.789768 19293 update.go:89] pod "downloads-849b6cd45c-r2z6r" removed (evicted) This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1745772 (look at the 600s spent evicting the download pod which just slows things down, it's not actually making the cluster fail the upgrade) *** This bug has been marked as a duplicate of bug 1745772 ***