Skip to content

Commit

Permalink
Handle simulating conductor readiness
Browse files Browse the repository at this point in the history
Looks like during some async operations we
can simulate readines too fast. To avoid this issue
we should handle this in eventually statement
  • Loading branch information
mrkisaolamb authored and openshift-merge-bot[bot] committed Jul 24, 2024
1 parent 72e2b1c commit b2aa553
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion test/functional/base_test.go
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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))
Expand Down

0 comments on commit b2aa553

Please sign in to comment.