-
Bug
-
Resolution: Won't Do
-
Critical
-
4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Rejected
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
(Feel free to update this bug's summary to be more specific.)
Component Readiness has found a potential regression in the following test:
[sig-network] pods should successfully create sandboxes by writing network status
Significant regression detected.
Fishers Exact probability of a regression: 100.00%.
Test pass rate dropped from 100.00% to 93.65%.
Sample (being evaluated) Release: 4.18
Start Time: 2025-02-03T00:00:00Z
End Time: 2025-02-10T12:00:00Z
Success Rate: 93.65%
Successes: 57
Failures: 4
Flakes: 2
Base (historical) Release: 4.17
Start Time: 2024-09-01T00:00:00Z
End Time: 2024-10-01T23:59:59Z
Success Rate: 100.00%
Successes: 262
Failures: 0
Flakes: 3
View the test details report for additional context.
- blocks
-
OCPBUGS-55724 etcd timeouts causing failed pod sandbox creation writing network status
-
- Closed
-
- is cloned by
-
OCPBUGS-53148 Component Readiness: [sig-network] pods should successfully create sandboxes by writing network status - etcd timed out for request
-
- Closed
-
-
OCPBUGS-55724 etcd timeouts causing failed pod sandbox creation writing network status
-
- Closed
-
- is duplicated by
-
OCPBUGS-53449 pod-network-avalibility setup failing more in 4.19
-
- Closed
-
- is related to
-
OCPBUGS-53449 pod-network-avalibility setup failing more in 4.19
-
- Closed
-
- relates to
-
TRT-2061 Investigate API load from monitortest init
-
- Closed
-
-
TRT-2062 Breakout new pod sandbox invariant for etcdserver timeouts specifically
-
- Closed
-
- links to