You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a fresh Azure cloud-shell bash session, with az aks get-credentials ran, then kubelogin convert-kubeconfig -l azurecli. we found kubectl get nodes to be stuck.
checking kubelogin get-token --login azurecli --server-id <redacted> -v 99, I realize it is stuck on:
Unfortunately there isn't much logged all the way until it times out with those messages:
Error: failed to get token: expected an empty error but received: AzureCLICredential: ERROR: Failed to connect to MSI. Please make sure MSI is configured correctly.
This error goes away if I explicitly run az login. It looks like NewAzureCLICredential-->GetToken does something unexpected with the vanilla cloud-shell credentials.
The text was updated successfully, but these errors were encountered:
Hi,
I have a fresh Azure cloud-shell bash session, with
az aks get-credentials
ran, thenkubelogin convert-kubeconfig -l azurecli
. we foundkubectl get nodes
to be stuck.checking
kubelogin get-token --login azurecli --server-id <redacted> -v 99
, I realize it is stuck on:Unfortunately there isn't much logged all the way until it times out with those messages:
This error goes away if I explicitly run
az login
. It looks likeNewAzureCLICredential-->GetToken
does something unexpected with the vanilla cloud-shell credentials.The text was updated successfully, but these errors were encountered: