-
Notifications
You must be signed in to change notification settings - Fork 147
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
Airlock deployment failed #3586
Comments
Hi @Danny-Cooke-cCK The operation logs can be retrieved by using the Swagger UI for the API. at https://<tre_id>.region>.cloudapp.azure.com/api/workspaces/<workspace_id>/docs Let us know why it failed and can advise. We have fixed some issues around deleting failed resources in the main branch, but yet to be released. |
Have you clicked the authorise button at the top, and logged in? Leave client secret blank. |
Staringly i can't. |
just looked at th swagger documentation and figured the login out. The install logs just said "awaiting install" |
Can you paste the full JSON from the operations API endpoint? Do you know if you ran any make commands while deployment was in progress? |
Closing as required fix are in base workspace and need to be included in airlock as covered in #3617 |
During the deploy of a whole new TRE environment at version 11, the airlock workspace deployment hangs with a message that says "authorization not yet deployed for resource" and then eventually fails
in this state we can't disable and delete as it errors again with another message advising it can't be disabled.
we then deployed a second airlock workspace and this went through fine while the original deployment has decided to start performing an upgrade.
so this bug is being raised because the first one failed and can't be removed. and the second one worked fine. unsure of where to fine the logs to see what happened.
The text was updated successfully, but these errors were encountered: