[Feature:Builds][webhook] TestWebhook [Suite:openshift/conformance/parallel] failed in four of the last ten runs on https://testgrid.k8s.io/redhat-openshift-release-informing#redhat-canary-openshift-ocp-installer-e2e-gcp-4.2&sort-by-failures= . To meet our objectives, the overall failure rate must be 1/4, this exceeds that. Link to a job showing the failure: https://prow.k8s.io/view/gcs/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-gcp-4.2/260
From what I can find in the logs, the actual error that is occurring is not bubbling up through the WaitForAccessAllowed call in the "adding to binding" step of this specific test. But it does seem that adding that specific binding is completing the Create step, but possibly the permissions are not being either 1.) reloaded or 2.) the cache is not being updated to support checking the newly created RoleBinding. It may be worth adding additional logging here, or maybe someone can point me to where the additional logs are located if they are already being written somewhere?
Seems that I can't edit my previous comment ... It also seems that this is not really an issue with the Build component but some kind of Auth issue?
Out of the last 14 runs, there were three failures that were unrelated to this bugzilla. The last three failures were caused by: #280 level=fatal msg="Bootstrap failed to complete: failed to wait for bootstrapping to complete: timed out waiting for the condition" #279 level=error msg="Error: Error waiting to create Image: Error waiting for Creating Image: timeout while waiting for state to become 'DONE' (last state: 'RUNNING', timeout: 4m0s)" #275 fail [k8s.io/kubernetes/test/e2e/framework/framework.go:338]: Sep 15 14:34:54.275: Couldn't delete ns: "e2e-test-build-webhooks-ht54s": namespace e2e-test-build-webhooks-ht54s was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed (&errors.errorString{s:"namespace e2e-test-build-webhooks-ht54s was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed"})
Ok, ignore all of that, the real issue is https://prow.k8s.io/view/gcs/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-gcp-4.2/260#0:build-log.txt%3A7194 Sep 13 16:17:16.745: INFO: Couldn't delete ns: "e2e-test-build-webhooks-dbqzv": namespace e2e-test-build-webhooks-dbqzv was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed (&errors.errorString{s:"namespace e2e-test-build-webhooks-dbqzv was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed"}) ... fail [k8s.io/kubernetes/test/e2e/framework/framework.go:338]: Sep 13 16:17:16.745: Couldn't delete ns: "e2e-test-build-webhooks-dbqzv": namespace e2e-test-build-webhooks-dbqzv was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed (&errors.errorString{s:"namespace e2e-test-build-webhooks-dbqzv was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed"})
Verified in version: 4.2.0-0.nightly-2019-09-19-004703 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-gcp-4.2/337
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922