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
`[23:27:30] info Workspace dev-azure-com already exists
[23:27:42] fatal prepare workspace client: resolve option AZURE_PROVIDER_TOKEN: run command: exec command: DefaultAzureCredential: failed to acquire a token.
Attempted credentials:
EnvironmentCredential: missing environment variable AZURE_TENANT_ID
WorkloadIdentityCredential: no client ID specified. Check pod configuration or set ClientID in the options
ManagedIdentityCredential: Get "http://169.254.169.254/metadata/identity/oauth2/token": dial tcp 169.254.169.254:80: connectex: A socket operation was attempted to an unreachable network.
AzureCLICredential: exit status 1
AzureDeveloperCLICredential: Azure Developer CLI not found on path
: exit status 1
and variants of it using the latest Azure provider and a slightly older one, stock setup USEast2. If I keep hammering it often it comes online, but it seems super weird in terms of how its connecting. But the debug logs don't help me figure out where the issue is.
The text was updated successfully, but these errors were encountered:
Heu @buggtb, to me it looks like this could be the case when you're not logged into azure through the azure CLI?
I'm not sure about your orgs settings but I usually have to reauthenticate before doing anything with it.
The debug logs you see are the azure go sdk basically trying different methods to authenticate you:
From the environment
WorkloadIdentity from within a kubernetes cluster
ManagedIdentity is usually used when Azure creates infra for you and assigns a managed identity to that instance, i.e. the VM
Azure cli: This is the local azure CLI. Based on exit status 1 it looks like this might be the culprit here. It's basically running az account get-access-token -o json --resource $YOUR_RESOURCE --subscription $YOUR_SUBSCRIPTION. It depends on your account setup what exactly needs to be filled in here but I assume running the full command might give you more insights
DevPod could still do a better job of exposing these issues though
Using devpod 0.6.5
I see this a lot
and variants of it using the latest Azure provider and a slightly older one, stock setup USEast2. If I keep hammering it often it comes online, but it seems super weird in terms of how its connecting. But the debug logs don't help me figure out where the issue is.
The text was updated successfully, but these errors were encountered: