Open BzSpi opened 2 years ago
route to CXP team
Is there a work-around? The CR cannot be changed via Azure Portal and the CLI is broken. We're now stuck with a more-or-less unusable workspace.
Hello @BzSpi @chriswue
Thank you for reporting this issue, we are routing this to service Teams' attention!
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureml-github.
Author: | BzSpi |
---|---|
Assignees: | - |
Labels: | `Service Attention`, `Machine Learning`, `customer-reported`, `Auto-Assign` |
Milestone: | Backlog |
@SatishBoddu-MSFT please confirm if this is still an active issue.
Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!
Do not close
@mingweihe could you please take a look at this issue?
Hi @BzSpi , happy new year, thanks for the request.
The argument has been changed. Please update the CLI version by following the guides on this page: https://learn.microsoft.com/en-us/azure/machine-learning/how-to-configure-cli?tabs=public
Then use the new argument -u/--update-dependent-resources instead. https://learn.microsoft.com/en-us/cli/azure/ml/workspace?view=azure-cli-latest#az-ml-workspace-update
A full command line could be
az ml workspace update -g <resource group name> -n <workspace name> --container-registry <ACR arm ID> -u
Last time I tried the -u
option (v2.5.0), the update was still being refused and I had to "manually" invoke the PATCH
request myself instead with Postman (sorry I do not have a workspace available to test it again on)
I want to write and confirm that I DID get this to work with azure-cli 2.53.1 and ml 2.21.1
Here is the command that worked:
az ml workspace update -n {workspace name} -g {resource group name} --container-registry {NEW registry ID} -u
Note that the {NEW registry ID} is the full path such as:
container-registry/subscriptions/{subscriptionID}/resourceGroups/{resourcegroupID}/providers/Microsoft.ContainerRegistry/registries/{registryID}
I want to make this change, but I want to know if this will change anything on the workspace (will anything be deleted?) I can't find an answer to this question anywhere.
Describe the bug When trying to update a Machine Learning Workspace container registry, I have the following message:
And when I use the same command with the
--yes
flag, Azuz CLI yields that argument is not recognizedTo Reproduce Use the commands above.
Expected behavior It updates the machine learning workspace associated registry.
Environment summary
Additional context I use the v2 extension.