Known issue - Creating compute instance after a workspace move results in an Etag conflict error.
APPLIES TO:
Azure CLI ml extension v2 (current)
Python SDK azure-ai-ml v2 (current)
After a moving a workspace to a different subscription or resource group, creating a compute instance with the same name as a previous compute instance will fail with an Etag conflict error.
Status: Open
Problem area: Compute
Symptoms
After a workspace move, creating a compute instance with the same name as a previous compute instance will fail due to an Etag conflict error.
When you make a workspace move the compute resources aren't moved to the target subscription. However, you can't use the same compute instance names that you were using previously.
Solutions and workarounds
To resolve this issue, use a different name for the compute instance.
Next steps
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for