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".
- account is impacted by
-
OCPBUGS-19490 "[sig-arch] events should not repeat pathologically for ns/openshift-machine-api" test case is failing continously in 4.14 PowerVS builds
- Verified
- blocks
-
OCPBUGS-33367 [Jira:"NetworkEdge"] monitor test service-type-load-balancer-availability setup fails frequently in 4.14 & 4.15 PowerVS CI jobs
- Closed
-
OCPBUGS-33368 [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-23360 [Jira:"NetworkEdge"] monitor service-type-load-balancer-availablity test fails frequently in 4.14 PowerVS MAC CI jobs
- Closed
-
OCPBUGS-33367 [Jira:"NetworkEdge"] monitor test service-type-load-balancer-availability setup fails frequently in 4.14 & 4.15 PowerVS CI jobs
- Closed
-
OCPBUGS-33368 [Jira:"NetworkEdge"] monitor test service-type-load-balancer-availability setup fails frequently in 4.14 & 4.15 PowerVS CI jobs
- Closed
- is duplicated by
-
OCPBUGS-23284 [IBM VPC] "NetworkEdge" monitor test service-type-load-balancer-availability setup fails
- Closed
- links to
-
RHBA-2024:2865 OpenShift Container Platform 4.15.z bug fix update