Reconcile loop while setting Ready state on Core Provider

[swarren83]

What steps did you take and what happened:

1. Install CAPI Operator v0.24.0
2. Install CAPI Core Provider v1.11.0

CAPI Operator installing CAPI Core Provider, but is unable to make it ready. The "Ready" patch fails due to an invalid value of an empty string in status.conditions[0].message

E1110 22:44:20.442691       1 controller.go:353] "Reconciler error" err="failed to patch CoreProvider capi-system/cluster-api: CoreProvider.operator.cluster.x-k8s.io \"cluster-api\" is invalid: status.conditions[0].message: Invalid value: \"\": conditions[0].message in body should be at least 1 chars long" controller="healthcheck-operator.cluster.x-k8s.io/v1alpha2, Kind=CoreProvider" controllerGroup="apps" controllerKind="Deployment" Deployment="capi-system/capi-controller-manager" namespace="capi-system" name="capi-controller-manager" reconcileID="2f9f565a-df92-4dd0-95c6-06901a740848"

What did you expect to happen:
CAPI Core Provider installed and set Ready if healthy.

Anything else you would like to add:
Using Rancher v2.11.3 and helm to install CAPI Operator and CAPI CoreProvider

Environment:

• Cluster-api-operator version: v0.24.0
• Cluster-api version: v1.11.x
• Rancher version: v2.11.3
• Kubernetes version: (use kubectl version): 1.31.10, 1.32.9
• OS (e.g. from /etc/os-release): rocky 9

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

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.