Airlock Container not always created succesfully

[marrobi]

When creating an airlock request the container is not always successfully created. This has been noticed before, but now seen in e2e tests:

https://github.com/microsoft/AzureTRE/actions/runs/13975180861/job/39177589907

INFO     e2e_tests.test_airlock:test_airlock.py:53 try #45 to upload a blob to container
 ....
INFO     e2e_tests.test_airlock:test_airlock.py:63 sleeping for 30 sec until container would be created

[SiobhanBaynes]

@marrobi assign to me please

[marrobi]

@SiobhanBaynes thanks, let us know if you can get a consistent reproduction.

I'm tempted to just try creating a 100 containers using the Azure Python SDK and see if they all succeed.

[SiobhanBaynes]

Having difficulty repro'ing this. Ran a script to create 1000 airlock import requests via the API and then poll the storage account to time how long before the container was created. Average was 5 seconds with very little standard deviation.

Best guess is there could be a race condition between the function app and the private endpoint on the storage account such that on occasion the FA can't access the SA. Adding a manual dependency between the two to ensure the PE is created before the FA.

[marrobi]

I think this is the cause of e2e failing , so should merge this fix.