cluster-api-provider-azure: e2e tests logs are missing the entire controller manager logs

/kind bug

[Before submitting an issue, have you checked the Troubleshooting Guide?]

What steps did you take and what happened: [A clear and concise description of what the bug is.] The job https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-provider-azure#capz-periodic-e2e-full-main is missing the full set of controller manager logs. If you look for vmss in

• https://storage.googleapis.com/kubernetes-jenkins/logs/periodic-cluster-api-provider-azure-e2e-full-main/1461402439272894464/artifacts/clusters/bootstrap/controllers/capi-controller-manager/capi-controller-manager-6bdc78c4d4-nnxc7/manager.log
• https://storage.googleapis.com/kubernetes-jenkins/logs/periodic-cluster-api-provider-azure-e2e-full-main/1461402439272894464/artifacts/clusters/bootstrap/controllers/capz-controller-manager/capz-controller-manager-5f7b59585c-m9lxd/manager.log

you will not find relevant logs for that cluster even though the cluster was created: https://gcsweb.k8s.io/gcs/kubernetes-jenkins/logs/periodic-cluster-api-provider-azure-e2e-full-main/1461402439272894464/artifacts/clusters/capz-e2e-4e4w9c-win-vmss/machines/

What did you expect to happen:

Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

~My guess is the logs are rolling and we are missing the first part of the logs~

Environment:

• cluster-api-provider-azure version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):