build pod already exists and is older than the build
stevekuznetsov opened this issue · comments
Just hit this on my PR #313 -- the first round of tests had every single test fail with:
2019/04/04 03:16:59 Building src
2019/04/04 03:17:00 Build src failed, printing logs:
2019/04/04 03:17:00 error: Unable to retrieve logs from failed build: build src is in an error state. No logs are available.
2019/04/04 03:17:11 Ran for 12s
error: could not run steps: could not wait for build: the build src failed after 0s with reason BuildPodExists: The pod for this build already exists and is older than the build.
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_ci-operator/313/pull-ci-openshift-ci-operator-master-unit/476
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_ci-operator/313/pull-ci-openshift-ci-operator-master-lint/473
https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_ci-operator/313/pull-ci-openshift-ci-operator-master-images/479
@openshift/developer-productivity-test-platform
I've never seen this before, has anyone else? @wking
Ah, one of the jobs has
2019/04/04 03:17:00 Building src
2019/04/04 03:17:00 Build src previously failed from an infrastructure error (CannotRetrieveServiceAccount), retrying...
2019/04/04 03:17:00 Build src failed, printing logs:
2019/04/04 03:17:00 error: Unable to retrieve logs from failed build: build src is in an error state. No logs are available.
2019/04/04 03:17:11 Ran for 12s
error: could not run steps: could not wait for build: the build src failed after 0s with reason BuildPodExists: The pod for this build already exists and is older than the build.
So it would seem that our build retry logic is bad