Filed from: Test Regression Details

Test Name

[sig-api-machinery] OrderedNamespaceDeletion namespace deletion should delete pod first [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s]

Brief Overview

This NEW test is marked regressed with a pass rate of 83.33%, which is below the required 95.00% threshold for new tests. The failures are related to namespace deletion not being processed by the namespace controller within the allotted time.

Statistics Section

This is a NEW test in this release, and must pass at a 95% success threshold, rather than being compared to historical data.

Sample Failure Outputs

• Job Run 1979603925552074752: fail [k8s.io/kubernetes/test/e2e/apimachinery/namespace.go:624]: context deadline exceeded
• Job Run 1979684812352393216: fail [k8s.io/kubernetes/test/e2e/apimachinery/namespace.go:575]: namespace e2e-nsdeletetest-1764 has not been processed by namespace controller: context deadline exceeded
• Job Run 1981075642027872256: fail [k8s.io/kubernetes/test/e2e/apimachinery/namespace.go:575]: namespace e2e-nsdeletetest-2068 has not been processed by namespace controller: context deadline exceeded
• Job Run 1980779116474929152: fail [k8s.io/kubernetes/test/e2e/apimachinery/namespace.go:575]: namespace e2e-nsdeletetest-2899 has not been processed by namespace controller: context deadline exceeded

Links to Relevant Jobs

• periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview
• periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview
• periodic-ci-openshift-release-master-ci-4.21-e2e-gcp-ovn-techpreview
• periodic-ci-openshift-release-master-nightly-4.21-e2e-gcp-ovn-runc-techpreview

Patterns and Insights

The failures are consistent across multiple job runs and indicate a problem with namespace deletion. The common error message "context deadline exceeded" or "namespace ... has not been processed by namespace controller: context deadline exceeded" suggests a timeout issue where the namespace controller is not deleting namespaces in a timely manner.

This is a new test in the 4.21 release arriving via the k8s rebase, and it is failing to meet the 95% success rate threshold.

As such this is treated as a release blocker as it does not meet our quality thresholds for release.

Filed by: dgoodwin@redhat.com