-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18
-
None
-
Approved
-
False
-
Component Readiness has found a potential regression in the following tests:
Undiagnosed panic detected in pod
Extreme regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 100.00% to 83.33%.
[sig-arch] events should not repeat pathologically for ns/openshift-cluster-csi-drivers
Extreme regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 100.00% to 0.00%.
API LBs follow /readyz of kube-apiserver and stop sending requests before server shutdowns for external clients
Test has a 61.11% pass rate, but 95.00% is required.
[sig-architecture] platform pods in ns/default should not exit an excessive amount of times
Test has a 88.89% pass rate, but 95.00% is required.
[sig-arch][Late] clients should not use APIs that are removed in upcoming releases [apigroup:apiserver.openshift.io] [Suite:openshift/conformance/parallel]
Extreme regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 100.00% to 84.00%.
[sig-storage][Feature:CSIInlineVolumeAdmission][Serial] restricted namespace should deny pods with inline volumes when the driver uses the privileged label [Suite:openshift/conformance/serial]
Test has a 94.74% pass rate, but 95.00% is required.
[sig-storage][Feature:CSIInlineVolumeAdmission][Serial] baseline namespace should allow pods with inline volumes when the driver uses the restricted label [Suite:openshift/conformance/serial]
Test has a 94.74% pass rate, but 95.00% is required.
[sig-storage][FeatureGate:VSphereDriverConfiguration][Serial][apigroup:operator.openshift.io] vSphere CSI Driver Configuration snapshot options in clusterCSIDriver should allow setting global snapshot limit [Suite:openshift/conformance/serial]
Test has a 94.74% pass rate, but 95.00% is required.
Undiagnosed panic detected in pod
Significant regression detected.
Fishers Exact probability of a regression: 99.99%.
Test pass rate dropped from 100.00% to 90.62%.
[sig-storage][FeatureGate:VSphereDriverConfiguration][Serial][apigroup:operator.openshift.io] vSphere CSI Driver Configuration snapshot options in clusterCSIDriver should allow setting VSAN limit [Suite:openshift/conformance/serial]
Test has a 94.74% pass rate, but 95.00% is required.
[Jira:"Test Framework"] monitor test initial-and-final-operator-log-scraper collection
Test has a 94.74% pass rate, but 95.00% is required.
[sig-network-edge][Feature:Idling] Unidling with Deployments [apigroup:route.openshift.io] should handle many TCP connections by possibly dropping those over a certain bound [Serial] [Suite:openshift/conformance/serial]
Test has a 94.74% pass rate, but 95.00% is required.
[Jira:"Networking / On-Prem Host Networking"] monitor test on-prem-haproxy collection
Test has a 94.74% pass rate, but 95.00% is required.
[sig-storage][Feature:CSIInlineVolumeAdmission][Serial] privileged namespace should allow pods with inline volumes when the driver uses the restricted label [Suite:openshift/conformance/serial]
Test has a 94.74% pass rate, but 95.00% is required.
[sig-storage][Feature:CSIInlineVolumeAdmission][Serial] baseline namespace should deny pods with inline volumes when the driver uses the privileged label [Suite:openshift/conformance/serial]
Test has a 94.74% pass rate, but 95.00% is required.
[Jira:"kube-apiserver"] monitor test api-unreachable-from-client-metrics collection
Test has a 94.74% pass rate, but 95.00% is required.
[sig-api-machinery][Feature:APIServer][Late] kubelet terminates kube-apiserver gracefully extended [Suite:openshift/conformance/parallel]
Test has a 94.74% pass rate, but 95.00% is required.
Useful Component Readiness Links:
We are proving the following two links for your convenience:
- Click here to access a snapshot of the component readiness page at the time this issue was generated.
- Click here to access the component readiness page with latest data. This is useful for developers to verify their fixes.
Workflow Requirement:
This is an automatically generated Jira card against the component based on stats generated from component readiness dashboard. Please follow the following requirements when dealing with this card:
- Please use this card as a placeholder for all the regressed tests for your component. A separate issue should be created for each regressed test and linked to this issue. Please only close this issue when all known regressed tests are believed fixed.
- Please do not remove 'Release Blocker' label. The bot will automatically add it back if any regressed tests continue showing for the component.