-
Bug
-
Resolution: Done
-
Major
-
None
-
5
-
False
-
-
False
-
-
-
GitOps Crimson Sprint 23
The following kuttl tests are failing during kuttl test execution only on lower OCP version (4.12).
Notably, the Redis HA-related tests do pass if the timeout is increased to ~1200s (20 mins), but fail under the default timeout.
It appears that the Redis pods are taking longer than expected to come up on these versions, leading to timeouts.
Parallel tests:
- 1-065_validate_redis_ha_anti_affinity
ArgoCD deployment stayed in a Pending state and timed out.
Redis pods did not become ready within the default timeout.
- 1-069_validate_redis_secure_comm_autotls_ha
Redis HA deployment only had 1 replica instead of the required 3 within the timeout window.Redis pods took a long time to schedule/startup.
- 1-067_validate_redis_secure_comm_no_autotls_ha
Redis HA StatefulSet failed to report readyReplicas.
Indicates Redis pod startup delays.
Sequential tests:
- 1-020_validate_redis_ha_nonha
After enabling Redis HA, the ArgoCD resource was stuck in Pending.
Redis pods were slow to come up, resulting in timeout.