Describe the bug
Unable to connect to the applications on an AML Compute Instance after installing an aml_compute user resource. The errors are various depending on the Application:
Terminal or Notebook
When attempting to run either a Terminal or Notebook application, the following error message appears: 'You do not have access to the workspace storage account. The storage may be behind a VNET'. I have then changed the configuration settings for the AML Storage Service by setting 'Allow Storage Account Key Access' to 'enabled'. Whilst this appears to fix the 'storage account access' problem, when attempting to run a Notebook, there's a new error message: 'kernel not connected'. I don't appear to be able to select a kernel from the dropdown menu in the AML UI:
JupyterLab and Jupyter
When attempting to run JupyterLab or Jupyter, I'm first presented with a 'site unreachable' error, with connection to 'auth.uksouth.instances.azureml.ms'. If I add a Firewall rule for this FQDN, then I get the following message when re-connecting to JupyterLab and Jupyter applications: 'This compute instance doesn't appear to be connectable. Check to make sure it's started. If you just started it, please wait a little longer.' But waiting longer doesn't fix the issue.
Steps to reproduce
- TRE Deployed via AzureTRE Template repository using 'Manual' deployment.
- Deploy AML Workspace Service (Public Access: Disabled)
- Add an AML Compute User Resource assigned to my user object-id
- Connect to the AML Workspace via a Guacamole VM, logging-in with the same object id used in (2)
- Attempt to connect to JupyterLab, Jupyter, Notebooks or Terminal from the 'Applications' section of the running compute instance.
Similar issues occur if I create an AML Workspace service with 'Public Access: Enabled' (apart from the firewall issue).
Azure TRE release version (e.g. v0.14.0 or main):
v0.28.0
Deployed Azure TRE components - click the (i) in the UI:
UI Version: 0.8.26
API Version: 0.25.14
Template Versions:
tre-workspace-base: 2.8.2
tre-service-azureml: 1.1.3
tre-user-resource-aml-compute-instance: 0.5.12
Describe the bug
Unable to connect to the applications on an AML Compute Instance after installing an aml_compute user resource. The errors are various depending on the Application:
Terminal or Notebook
When attempting to run either a Terminal or Notebook application, the following error message appears: 'You do not have access to the workspace storage account. The storage may be behind a VNET'. I have then changed the configuration settings for the AML Storage Service by setting 'Allow Storage Account Key Access' to 'enabled'. Whilst this appears to fix the 'storage account access' problem, when attempting to run a Notebook, there's a new error message: 'kernel not connected'. I don't appear to be able to select a kernel from the dropdown menu in the AML UI:
JupyterLab and Jupyter
When attempting to run JupyterLab or Jupyter, I'm first presented with a 'site unreachable' error, with connection to 'auth.uksouth.instances.azureml.ms'. If I add a Firewall rule for this FQDN, then I get the following message when re-connecting to JupyterLab and Jupyter applications: 'This compute instance doesn't appear to be connectable. Check to make sure it's started. If you just started it, please wait a little longer.' But waiting longer doesn't fix the issue.
Steps to reproduce
Similar issues occur if I create an AML Workspace service with 'Public Access: Enabled' (apart from the firewall issue).
Azure TRE release version (e.g. v0.14.0 or main):
v0.28.0
Deployed Azure TRE components - click the (i) in the UI:
UI Version: 0.8.26
API Version: 0.25.14
Template Versions:
tre-workspace-base: 2.8.2
tre-service-azureml: 1.1.3
tre-user-resource-aml-compute-instance: 0.5.12