capz-controller-manager fails to get api resources about cluster-api-provider-azure HOT 9 CLOSED

Thanks for coming back here and letting us know what fixed it! Going to close this for now since you're both unblocked, feel free to open follow up issues for anything that could have made this easier to debug.

/close

from cluster-api-provider-azure.

Does this error persist if you uninstall CAPI/CAPZ and reinstall it? are all the pods healthy on the management cluster besides the CAPZ manager? I've seen this error happen transiently once in a test when cert-manager was not running

from cluster-api-provider-azure.

I'm running into something similar, but not sure it's the same bug.

E1027 23:44:59.733236       1 controller.go:324]  "msg"="Reconciler error" "error"="failed to create scope: failed to configure azure settings and credentials for Identity: failed to create copied AzureIdentity brcox-hypershift-arm-clusters-brcox-hypershift-arm-brcox-hypershift-arm in capz-system: failed to get API group resources: unable to retrieve the complete list of server APIs: aadpodidentity.k8s.io/v1: the server could not find the requested resource" "AzureMachine"={"name":"brcox-hypershift-arm-f412695a-jnk28","namespace":"clusters-brcox-hypershift-arm"} "controller"="azuremachine" "controllerGroup"="infrastructure.cluster.x-k8s.io" "controllerKind"="AzureMachine" "name"="brcox-hypershift-arm-f412695a-jnk28" "namespace"="clusters-brcox-hypershift-arm" "reconcileID"="6af4e450-887d-4c13-9ac3-a0d6e72305a4"

from cluster-api-provider-azure.

@bryan-cox same questions as above

Also found this from a quick search helm/helm#6361 (comment)

Can you check kubectl get apiservices?

from cluster-api-provider-azure.

I'll run that command and see.

I had deleted the pod but didn't try a new cluster or something like that.

from cluster-api-provider-azure.

Ran that command on my mgmt cluster this morning. I didn't have any apiservices where AVAILABLE was False.

from cluster-api-provider-azure.

For me, specifically specifying the bootstrap / control plane providers fixed the issue.

# This caused the issue mentioned above
clusterctl init -b talos -c talos -i sidero
clusterctl init -i azure

# This works fine
clusterctl init -b talos -c talos -i sidero
clusterctl init -i azure -b kubeadm -c kubeadm

from cluster-api-provider-azure.

I got past my issue. It was a setup issue. I needed to set the AzureClusterIdentity type to ManualServicePrincipal and my secret ref was missing the key clientSecret.

from cluster-api-provider-azure.

@CecileRobertMichon: Closing this issue.

from cluster-api-provider-azure.