Open JesperPVS opened 9 months ago
hey @JesperPVS
Thanks for opening this issue.
Taking a quick look into this, the error message that Terraform is surfacing here is coming from the Azure API:
Code="OperationFailed" Message="Operation failed with general exception."
.. and as such this issue would need to be fixed within the Container App Environment API, rather than something we can necessarily workaround within Terraform - out of interest does the Activity Log for this Resource show any additional information?
Thanks!
hey @JesperPVS
Thanks for opening this issue.
Taking a quick look into this, the error message that Terraform is surfacing here is coming from the Azure API:
Code="OperationFailed" Message="Operation failed with general exception."
.. and as such this issue would need to be fixed within the Container App Environment API, rather than something we can necessarily workaround within Terraform - out of interest does the Activity Log for this Resource show any additional information?
Thanks!
Hey @tombuildsstuff,
In the Activity Log for the resource, the only thing it states is the following: For transparency; I deployed the resource again, to view the Activity Log, as I had deleted the one created from the output shown in the originating post.
The timestamp of the changed property is set between two statements in Terraform, as shown here: (Don't mind the changed resource names, all settings are as stated in my initial post.)
Discrepancies in timestamps are due to timezones being GMT on our pipeline agents, while being GMT+1 on my local system.
Hey @tombuildsstuff,
Found out what might possibly be the issue.. The subnet attribute for container app env in terraform seems to be case-sensitive, while the subnets in azure aren't.
Is there an existing issue for this?
Community Note
Terraform Version
1.7.0
AzureRM Provider Version
3.87.0
Affected Resource(s)/Data Source(s)
azurerm_container_app_environment
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
A Container App Environment with Internal Load Balancer and BYO Infrastructure subnet should be created, and ready for further tasks and/or configurations.
Actual Behaviour
Azure Container App Environment creation actually succeeds, as the resource is created in Azure, but Terraform fails on its polling, and thus thinks the resource failed to create.
The failure seems to happen when at a point, where I, in the Azure Portal, can see the resource is assigned an IP address from the infrastucture subnet. - I do not know where this causes the issue, just that the timing on the two things, seems to align.
Steps to Reproduce
terraform init
terraform plan
terraform apply
Important Factoids
No response
References
No response