ms-zhenhua
commented
1 year ago Hi @Holmern, thank you for reaching out. From the error message, it seems that it is the Azure Service who did not respond the request of creating subscription. Do you always meet this issue? If so, could you kindly add 2 environment variables TF_LOG="DEBUG" and TF_LOG_PATH=\<your local directory> according to this document and recreate the subscription by Terraform? Then could you please provide the log(you could first remove any sensitive data) to us to have a further investigation? Thanks.
Holmern
Is there an existing issue for this?
Community Note
Terraform Version
1.3.5
AzureRM Provider Version
3.30.0
Affected Resource(s)/Data Source(s)
azurerm_subscription
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Apply the subscription
Actual Behaviour
Pipeline fails with error: │ Error: creating new Subscription (Alias "472dfbe3-4b90-4ddd-97f9-887a803e16d7"): subscription.AliasClient#Create: Failure sending request: StatusCode=0 -- Original Error: context deadline exceeded
Steps to Reproduce
When running our GitHub Actions pipeline with apply, the output returns a [still creating], it does this for 30 minuts until the pipeline throws an error which states: Original Error: context deadline exceeded. The thing is, I did apply and create the prod subscription, but it won't create the "dev" subscription. Is there something I can do for getting a quicker apply and then provision the Subscription? Internet speed, to many resources that want to apply at the same time (even if we are down to 4 resources) or just bad luck and try again tomorrow
Important Factoids
West Europe
References
non