The compute instance name is hardcoded in quick_setup.ps1, but is required to be unique within the Azure region. Creation is likely to fail with a message similar to:
ERROR: {'Azure-cli-ml Version': '1.41.0', 'Error': ComputeTargetException:
Message: Compute name 'notebookScryptExecutor' is not available. Reason: AlreadyExists. Message: The specified name notebookScryptExecutor is already in use and is therefore unavailable
InnerException None
ErrorResponse
{
"error": {
"message": "Compute name 'notebookScryptExecutor' is not available. Reason: AlreadyExists. Message: The specified name notebookScryptExecutor is already in use and is therefore unavailable"
}
}}
Modifying the script to change the name is an effective workaround.
https://github.com/microsoft/Templates-For-Dynamics-365-Supply-Chain-Management-Demand-Forecasting-With-Azure-Machine-Learning/blob/13bacba6ea50ee4b2697cdc25c3982a8e286b37b/quick_setup.ps1#L180
The compute instance name is hardcoded in quick_setup.ps1, but is required to be unique within the Azure region. Creation is likely to fail with a message similar to:
Modifying the script to change the name is an effective workaround.