-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Not able to run az ml folder attach #20150
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureml-github. Issue Details
Describe the bug To Reproduce Expected behavior
Environment summary
|
route to service team |
Relevant service team has been notified and is actively working on a fix. |
@rcavalieri819 To unblock you, could you please downgrade the azure-cli/azure-cli-core version to be less than 2.30.0? You can refer to this comment on how to downgrade the azure cli. #13331 |
This is an Issue effecting one of our pipelines as well. Specifically when running the |
@ranikamadurawe I have managed to workaround this by editing authentication.py in .Azure\cliextensions\azure-cli-ml\azureml\core. Removing the 'async_persist=False' parameter seems to have done thr trick. |
I tried @jhliberis method but was not working for me and then i tried downgrading az cli to 2.29.1 as suggested by @Mossaka , and downgrading worked for me. I am using self hosted agent and i ran below command for downgrading: |
Update: Now Azure CLI task is running with v2.30.0 in all the pipelines, I am getting the same error everywhere. Please help me find the fix or rollback to the previous version in Azure CLI Task. |
im having the same error, any updates? please |
Seeing the same error by running
|
Our error is in our releases in azurecli with the command: |
Getting the same error here, any news on updates or quick fixes? |
we were able to fix the issue in DevOps using the following (installing 2.29.2)
|
Thanks, @Jerry1309 this works great as a work-around, thanks for posting/sharing so we can all get temporarily unblocked! Silly comment, but could you edit your formatting so that the first/initial line is also included in the code block region? This initially didn't work for me b/c the COPY CODE feature of the site doesn't include the first line of your script and I missed porting it in my first-pass attempt at duplicating your success for our own pipeline :P (just a suggestion to save others some time troubleshooting if/when they also attempt to repro based on your post, thanks again!) |
Thanks @Jerry1309. I have blocked with this error when I tried MLOps Poc, my error is also same, I was able to resolve the issue with the workaround you provided. Script lines worked the exact same for me. Only change for me is, I need to add the "--allow-downgrades" option in the last command when I notice a downgrade error, and I tested in 'ubuntu-18.04'. |
Glad to know it worked for you, you might have missed the cli removal part. Option 2 in this documentation helped me https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?pivots=apt |
Still getting errors while running
Any help? |
did you add the cli software repo by running if sudo apt-get install azure-cli=2.29.2-1~bionic is not working for you try with sudo apt-get install azure-cli=2.29.2-1~focus hope you are following all the commands including the removal of the current version from the Agent apt-cache policy azure-cli |
Yes, Thanks. It solves that error by using I guess I need to write that step manually again. Update:Finally it works!!
|
I had the same issue with version 2.30. It did work with 2.29. I used the command below to change from 2.30 to 2.29. python -m pip install -U --force-reinstall pip pip install azure-cli==2.29 |
This is blocking for us (we are on MS hosted agents using az-cli 2.30.0, we cannot downgrade azure-cli-core to 2.29.0 as there is incompatibility between az-cli 2.30.0 and 2.29.0 see here) |
Downgrading to azure cli to 2.29 is causing new issues in downloading azure artifacts. As azure-devops extension is not compatible with it.
|
@pragasv , you need to do something like this:
|
@dkmiller thanks for the comment, when i tried the approach you suggested i ran into a following issue for the same service connection. Is this a known issue ?
also i was able to get the pipeline for the following version configurations now.
|
Thanks to this suggestion, I monkey-patched import azure.cli.core._profile
profile_init_orig = azure.cli.core._profile.Profile.__init__
def profile_init_new(__self, cli_ctx=None, storage=None, async_persist=False):
profile_init_orig(__self, cli_ctx, storage)
azure.cli.core._profile.Profile.__init__ = profile_init_new |
This still isn't fixed, and updates please? @dkmiller perhaps you can help? |
@pragasv, Downgrade to version |
Im facing the same error |
this issue got resolved with latest version of azml cli extension |
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! |
Describe the bug
az ml folder attach
was working with the previous az cli version2.29.1
vs2.30.0
.To Reproduce
az ml folder attach
Expected behavior
Instead of a success, we get:
Environment summary
Use azure-cli-ml from Azure DevOps agents
The text was updated successfully, but these errors were encountered: