-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
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
Deployment via CloudShell failes leaving the Terraform State corrupt #2
Comments
Error: creating Windows Virtual Machine "spoke-addc-vm" (Resource Group "vwan-microhack-spoke-rg"): compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: autorest/azure: Service returned an error. Status= Code="OperationNotAllowed" Message="Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: westeurope, Current Limit: 4, Current Usage: 4, Additional Required: 2, (Minimum) New Limit Required: 6. Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/CapacityExperienceBlade/Parameters/%7B%22subscriptionId%22:%22142bc295-642a-47af-9a7d-6831a93e3abf%22,%22command%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22westeurope%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22cores%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:6,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22cores%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limitsat https://docs.microsoft.com/en-us/azure/azure-supportability/regional-quota-requests" |
can some on help me with what needs to be done |
When deploying via cloud shell a timeout error could occour while obtaining a refresh token.
This will fail the terraform deployment and leaves the state in an corrupt state because the vwan is deployed but this is not reflected in the state file.
Redeploying will end up in an "already exists" error
This was reproduceable for me using the instructions in the repo.
Deploying from a local Terminal using Powershell Core will run through the deployment. This is a possible workaround.
The text was updated successfully, but these errors were encountered: