From b2aa553644ba600eb6a4f73be669cd637a9f0ad5 Mon Sep 17 00:00:00 2001 From: Kamil Sambor Date: Wed, 24 Jul 2024 16:58:28 +0200 Subject: [PATCH] Handle simulating conductor readiness Looks like during some async operations we can simulate readines too fast. To avoid this issue we should handle this in eventually statement --- test/functional/base_test.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/test/functional/base_test.go b/test/functional/base_test.go index 7c176d2f9..63772e06d 100644 --- a/test/functional/base_test.go +++ b/test/functional/base_test.go @@ -36,7 +36,7 @@ import ( const ( SecretName = "external-secret" ContainerImage = "test://nova" - timeout = 20 * time.Second + timeout = 25 * time.Second // have maximum 100 retries before the timeout hits interval = timeout / 100 // consistencyTimeout is the amount of time we use to repeatedly check @@ -830,6 +830,7 @@ func SimulateReadyOfNovaTopServices() { th.SimulateJobSuccess(cell0.CellMappingJobName) Eventually(func(g Gomega) { + th.SimulateStatefulSetReplicaReady(cell0.ConductorStatefulSetName) cell := GetNovaCell(cell0.CellCRName) g.Expect(cell.Status.Conditions.Get(condition.ReadyCondition).Status).To( Equal(corev1.ConditionTrue))