https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-upgrade/36 We were seeing flake rates in excess of 40% when upgrading a 4.2.2 GCP cluster to 4.3.0-0.ci. We had to disable the job yesterday, but this is blocking us spreading load to AWS and may indicate a more serious problem either in 4.3 or specifically on GCP.
Not sure why this was assigned to MCO... Double checked the logs and MCO and all pools are available and all MC* logs look fine. Reassigning..
This is not an actionable bug and has been inactive for a while. Closing.
This is still failing
May be a dupe of the apiserver shutdown failures
OK, could you please route this correctly, then?
This appears to be changing over time. There may have been a bug/dupe prior to 11/27, but that is gone now. The last 3 failures are this: "step needs a lease but no lease client provided" https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-upgrade/137 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-upgrade/136 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-upgrade/135 Let's mark this FIXED when that condition clears up (or dupe/link to an existing ticket)
There is no such error any longer.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days