Skip to content

Latest commit

 

History

History
38 lines (24 loc) · 1.42 KB

workspace-move-compute-instance-same-name.md

File metadata and controls

38 lines (24 loc) · 1.42 KB
Raw
title titleSuffix description author ms.author ms.topic ms.service ms.subservice ms.date ms.custom
Known issue - After a workspace move, creating a compute instance with the same name as a previous compute instance will fail
Azure Machine Learning
After 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.
s-polly
scottpolly
troubleshooting
machine-learning
core
08/14/2023
known-issue

Known issue - Creating compute instance after a workspace move results in an Etag conflict error.

[!INCLUDE dev v2]

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