module.airlock_resources.azurerm_service_plan.airlock_plan can take over 30 minutes to deploy

[TonyWildish-BH]

Description

In my Azure TRE deployment I am trying to run 'make deploy-core' on an as-yet unmodified fork. The deployment takes an excessively long time, and in particular, it seems that module.airlock_resources.azurerm_service_plan.airlock_plan is stuck somehow.

The resource is actually deployed, I can see it in the portal and it's there, healthy. However, terraform is not recognising that it has been deployed, and is waiting forever in the 'still creating' state.

N.B. There's some discussion at hashicorp/terraform-provider-azurerm#2616 which might be relevant?

Steps

The steps I have tried are:

1. Follow the build instructions to the letter, running step by step. When it comes to the 'deploy-core' target, I get this problem.
2. Killing/re-starting the process didn't help, it just picked up from where it was before.

Code

The code I am using is an unmodified fork of the source, last updated on December 7th. The latest entry in the 'git log' is:

Author: Marcus Robinson <marrobi@microsoft.com>
Date:   Thu Dec 7 16:12:25 2023 +0000

    Switch to Open Telemetry for logging (#3762)

[marrobi]

Hi @TonyWildish-BH not something I can see I've seen before.

as you say this is likely a TF provider or Azure issue, rather than the Azure TRE project itself.

Next steps would be to run terraform with debugging enable - https://developer.hashicorp.com/terraform/internals/debugging - somewhere in this file prior to the apply - devops/scripts/terraform_wrapper.sh . Then work out where the issue is and if it is the Terraform provider, raise an issue there.

Alternatively you could try deleting the plan in the Azure portal and see if TF recreates it. The plan doesn't hold any state so is safe to delete.

[TonyWildish-BH]

thanks Marcus, I'll try the debugging and see if that helps any.

I already tried deleting the plan in the portal. It got re-created, but terraform then got stuck waiting for it to complete, again.

I'm curious that nobody else has come across this before, just my luck :-(