Bug 1765749
| Summary: | [sig-api-machinery] Namespaces [Serial] should always delete fast (ALL of 100 namespaces in 150 seconds) | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anurag saxena <anusaxen> |
| Component: | kube-apiserver | Assignee: | Lukasz Szaszkiewicz <lszaszki> |
| Status: | CLOSED ERRATA | QA Contact: | Xingxing Xia <xxia> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3.0 | CC: | aos-bugs, ccoleman, mfojtik, pehunt, sttts |
| Target Milestone: | --- | ||
| Target Release: | 4.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-23 11:09:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
*** Bug 1765748 has been marked as a duplicate of this bug. *** This may be due to the revert of the namespace deletion code. It’s possible we missed one bit of it. This test has been very stable historically, and if we regressed namespace deletion that has impacts in other systems. Moving back to 4.3, I want to see this investigated. Since the PR merge and as of now, https://search.svc.ci.openshift.org/?search=should+always+delete+fast&maxAge=336h&context=2&type=all shows the case passed in all results and while https://search.svc.ci.openshift.org/?search=failed%3A+.*+should+always+delete+fast&maxAge=336h&context=2&type=all shows 0 failed, therefore moving to VERIFIED, thx. 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-2020:0062 |
Description of problem: fail [k8s.io/kubernetes/test/e2e/apimachinery/namespace.go:65]: Unexpected error: <*errors.errorString | 0xc00029c0f0>: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Additional info: https://testgrid.k8s.io/redhat-openshift-release-4.3-informing-ocp#release-openshift-ocp-installer-e2e-metal-serial-4.3 https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-metal-serial-4.3/185