-
Notifications
You must be signed in to change notification settings - Fork 148
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Docs Missing from Navigation and Airlock Docs (#3758)
Docs Missing from Navigation Fixes #3422
- Loading branch information
Showing
10 changed files
with
32 additions
and
96 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# Airlock Troubleshooting | ||
|
||
## Users cannot create Review VMs | ||
|
||
If a user sees an error when creating Review VMs, this most likely means that the configuration isn't correct. | ||
Double-check that all GUIDs don't have any symbols missing, and the names of templates are correct. | ||
|
||
[![Review VM Error](../assets/using-review-vm-errors.png)](../assets/using-review-vm-errors.png) | ||
|
||
|
||
## Files do not appear in Review Data folder on the VM | ||
|
||
If the Review Data folder is empty, it's likely because the review VM can't connect to the storage account. Import requests must be reviewed using a VM inside the workspace, and export requests must be reviewed using a VM outside the workspace. | ||
|
||
For imports ensure that the `airlock-import-review` workspace template is being used and configured in the airlock configuration for the workspace. | ||
|
||
|
||
## Airlock request does not move through the workflow as expected | ||
|
||
If the Airlock request does not move through the workflow as expected, it's likely an issue with the Azure Function that processes airlock requests. This function is deployed as part of the TRE, and can be found in the Azure Portal under the name `func-airlock-processor-<tre_id>`. | ||
|
||
To troubleshoot, view the function invocations starting with the StatusChangedQueue Trigger, then the other functions as shown in the image below: | ||
|
||
[![Function details](../assets/airlock_functions.png)](../assets/airlock_functions.png) | ||
|
||
Look for errors in the function invocations in the same time frame that the airlock request was created. Even if the function executed successfully, there may still be errors within the function invocation details. Invocations that take longer can also be a sign of an issue. For example: | ||
|
||
[![Functions error](../assets/airlock_functions_error.png)](../assets/airlock_functions_error.png) | ||
|
||
If this error should have been handled please create an issue on the GitHub repository for the Azure TRE. |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters