[Unit-test] Multiple test cases are failing in TestReconcileMachinePhases due to timeout

[arshadd-b]

Which jobs are flaking?

capi-test-main
capi-test-mink8s-main

Which tests are flaking?

TestReconcileMachinePhases/Should_set_Deletingwhen_Machine_is_being_deleted
TestReconcileMachinePhases/Should_setRunningwhen_bootstrap_and_infra_is_ready
TestReconcileMachinePhases/Should_setPending_with_a_new_Machine

Since when has it been flaking?

can see first occurrense on 9/6/2025
https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/periodic-cluster-api-test-mink8s-main/1964225995430957056

Testgrid link

https://testgrid.k8s.io/cluster-api-core-main#capi-test-main

Reason for failure (if possible)

dashboard link for more details
https://storage.googleapis.com/k8s-triage/index.html?job=.*cluster-api.*(test%7Ce2e)-(mink8s-)*main&test=TestReconcileMachinePhases&xjob=.*-provider-.*

Anything else we need to know?

No response

Label(s) to be applied

/kind flake
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

[sbueringer]

/triage accepted

[sbueringer]

/help

[k8s-ci-robot]

@sbueringer:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[arshadd-b]

I have tried this to run and reproduce locally but it is not reproducible
Then I tried to reduce the time from 10seconds to 1 second , could reproduce it locally
here

cluster-api/internal/controllers/machine/machine_controller_status_test.go

Line 2597 in 0e860e7

}, 10*time.Second).Should(BeTrue())

these tests mostly fail somewhere here

g.Expect(machine.Status.GetTypedPhase()).To(Equal(clusterv1.MachinePhaseDeleting)) nodeHealthyCondition := v1beta1conditions.Get(machine, clusterv1.MachineNodeHealthyV1Beta1Condition) g.Expect(nodeHealthyCondition).ToNot(BeNil()) g.Expect(nodeHealthyCondition.Status).To(Equal(corev1.ConditionFalse)) g.Expect(nodeHealthyCondition.Reason).To(Equal(clusterv1.DeletingV1Beta1Reason)) // Verify that the LastUpdated timestamp was updated g.Expect(machine.Status.LastUpdated.IsZero()).To(BeFalse()) g.Expect(machine.Status.LastUpdated.After(preUpdate)).To(BeTrue())

I think sometimes it is slow and we are not waiting enough ?
wanted to know your thoughts on it @sbueringer ?