We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when using the azurerm terraform provider, the coder provisioner returns an instance_id like
azurerm
instance_id
/subscriptions/05e8b285-4ce1-46a3-b4c9-f51ba67d6acc/resourceGroups/coder-spike-spikeaz-resources/providers/Microsoft.Compute/virtualMachines/coder-spike-spikeaz-vm
However the Coder Agent, using the Azure metadata service, calls Coder Server with vmId like: 90c8eeb0-597a-4df8-8ab6-dc25521d0989
vmId
This is rejected by Coder Server.
2022-07-29 17:58:40.865 [WARN] <./cli/agent.go:152> workspaceAgent.func1 authenticate workspace {"method": "azure-instance-identity", "error": "POST https://fccac451dc692c5a665d211025e3015e.pit-1.try.coder.app/api/v2/workspaceagents/azure-instance-identity: unexpected status code 404: Instance with id \"90c8eeb0-597a-4df8-8ab6-dc25521d0989\" not found."}
The text was updated successfully, but these errors were encountered:
Examining the terraform state, it looks like we need to grab virtual_machine_id from the state, rather than id
virtual_machine_id
id
Sorry, something went wrong.
kylecarbs
Successfully merging a pull request may close this issue.
when using the
azurerm
terraform provider, the coder provisioner returns aninstance_id
like/subscriptions/05e8b285-4ce1-46a3-b4c9-f51ba67d6acc/resourceGroups/coder-spike-spikeaz-resources/providers/Microsoft.Compute/virtualMachines/coder-spike-spikeaz-vm
However the Coder Agent, using the Azure metadata service, calls Coder Server with
vmId
like: 90c8eeb0-597a-4df8-8ab6-dc25521d0989This is rejected by Coder Server.
The text was updated successfully, but these errors were encountered: