-
Bug
-
Resolution: Done-Errata
-
Major
-
4.15
-
None
-
Moderate
-
No
-
Multi-Arch Sprint 253, Multi-Arch Sprint 254
-
2
-
False
-
-
Release Note Not Required
-
In Progress
This is a clone of issue OCPBUGS-18534. The following is the description of the original issue:
—
Description of problem:
Following tests fails consistently in 4.14 powerVS runs
- {}[Jira:"NetworkEdge"] XXXitor test service-type-load-balancer-availability setup
Issue 1 analysis:
Error Description :
{ failed during setup error waiting for replicaset: failed waiting for pods to be running: timeout waiting for 2 pods to be ready}Some Observations:
while creating a TCP service service-test with type=LoadBalancer for starting SimultaneousPodIPController it is failing to get loadbalancers details from cloud which is resulting to the error before starting data collection for e2e test and leading to the failure of test case "[Jira:"NetworkEdge"] XXXitor test service-type-load-balancer-availability setup".
- blocks
-
OCPBUGS-33781 [Jira:"NetworkEdge"] monitor test service-type-load-balancer-availability setup fails frequently in 4.14 & 4.15 PowerVS CI jobs
- Closed
- clones
-
OCPBUGS-18534 [Jira:"NetworkEdge"] monitor test service-type-load-balancer-availability setup fails frequently in 4.14 & 4.15 PowerVS CI jobs
- Closed
- is blocked by
-
OCPBUGS-18534 [Jira:"NetworkEdge"] monitor test service-type-load-balancer-availability setup fails frequently in 4.14 & 4.15 PowerVS CI jobs
- Closed
- is cloned by
-
OCPBUGS-33781 [Jira:"NetworkEdge"] monitor test service-type-load-balancer-availability setup fails frequently in 4.14 & 4.15 PowerVS CI jobs
- Closed
- links to
-
RHBA-2024:3673 OpenShift Container Platform 4.15.z bug fix update