-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AZ ML CLI login issue with MSI #2461
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureml-github. |
ml |
I installed
Judging by the error
auth, _, _ = profile_object.get_login_credentials(resource)
access_token = auth._token_retriever()[1] This is exactly the same coding fault as Azure/azure-cli#15805 (comment). @azureml-github, please refer to my comment to retrieve the token in the correct way. |
Hello, I have been used Azure-ml-cli since 1.18.0 and faced this issue for long time. Do we know when this will be fixed and released? |
@hyssh Thanks for the query. We are working on the fix and should be available two weeks from now with the next azure-cli-ml release. |
Is there a particular release this fixed is slated to go out with? |
This has been fixed in azure-cli-ml extension version 1.21.0. Please update the extension using the below command: az extension update --name azure-cli-ml |
Per the above posts, this issue was resolved with a fix at least two months ago. We'll now close this issue. |
Extension name (the extension in question)
azure-cli-ml
Description of issue (in as much detail as possible)
I'm trying to run a azure ml cli command using MSI identity the following way in a Azure VM (during a CICD pipeline run):
And getting this error:
I get this similar error in other Azure ML CLI commands like
az ml computetarget create amlcompute ...
Versions used:
However this was reproduceable at least with azure-cli 2.11.3 and 2.10.1
az login is working fine. This I know because ordinary Azure CLI commands are ran successfully during the same AZDO pipeline run in the same VM. Commands like this:
I also ran the same az ml datastore attach-blob commands locally using az login with my own user credentials (and same az-cli, az-ml-cli versions). These commands worked fine. This leads me to believe this issue concerns az ml cli and when using msi authentication
The text was updated successfully, but these errors were encountered: