Description of problem: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.2/51 fail [k8s.io/kubernetes/test/e2e/apimachinery/resource_quota.go:144]: Unexpected error: <*errors.errorString | 0xc000287400>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Version-Release number of selected component (if applicable): 4.2 jobs
dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1765704 ?
*** Bug 1768010 has been marked as a duplicate of this bug. ***
*** Bug 1765704 has been marked as a duplicate of this bug. ***
The first test case (from https://bugzilla.redhat.com/show_bug.cgi?id=1768010) timed out on "Counting existing ResourceQuota" step. The step simply tried to get a ResourceQuota object in a namespace, it gave up after 30 seconds. I suspected a network glitch. I checked the audit logs but I didn’t find a single request to “e2e-resourcequota-9242” namespace which is weird. The second test case (https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-mirrors-4.3/140) failed because the expected number of secrets didn’t match the actual in a ResourceQuota object (expected 3, actual 7). The number of expected secrets is calculated at the beginning of the test and basically boils down to looping until the number of secrets stabilizes for 5 seconds. As of today (1.17.1) the default number of secrets in a new namespace is 10. This particular test case run on v1.16.0-beta.2+04f4dcb The third test case (https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-gcp-4.2/51) failed on the same step as the second one only the actual values are different (expected 6, actual 9) and the version of the API server (v1.14.6)
Reopening since this test is consistently failing across multiple CI jobs. See [1] for additional detail. [1] https://search.svc.ci.openshift.org/?search=ResourceQuota+should+create+a+ResourceQuota+and+capture+the+life+of+a+secret&maxAge=48h&context=2&type=bug%2Bjunit
*** This bug has been marked as a duplicate of bug 1819849 ***