Skip to content
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

Failed to install any extension after upgrading to 2.66 version #30374

Open
RichardSunMS opened this issue Nov 18, 2024 · 4 comments
Open

Failed to install any extension after upgrading to 2.66 version #30374

RichardSunMS opened this issue Nov 18, 2024 · 4 comments
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Service Attention This issue is responsible by Azure service team. Similar-Issue

Comments

@RichardSunMS
Copy link

Describe the bug

When upgrading az cli to latest stable version 2.66, it failed to install any extension with error like complaining C:\Users{user}.azure\cliextensions

Related command

az extension add -n XXX

Errors

It's complaining the folder can't be removed or there is some content in it which need to be manually removed, but that folder doesn't exist at all.

Issue script & Debug output

NA

Expected behavior

extension could be installed successfully.

Environment Summary

2.66

Additional context

No response

@RichardSunMS RichardSunMS added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Nov 18, 2024
@yonzhan yonzhan added the Service Attention This issue is responsible by Azure service team. label Nov 18, 2024
@yonzhan
Copy link
Collaborator

yonzhan commented Nov 18, 2024

Please provide more detailed error info for us to troubeshoot

@ampandres
Copy link

The same problem started last Friday for us on the following extension az extension add -n rdbms-connect --allow-preview=true running on a Windows-latest agent. One thing I noticed today after getting one of our stages to run correctly was that the Python version on the agent is different.

For our current pipeline, we invoke this stage a couple of times, so it uses the same exact code. Below is one of the stages that was completed correctly without the warning error.

Image

Below is a future stage in the pipeline that failed with the same code but a different Python version.

Image

@bebound
Copy link
Contributor

bebound commented Nov 19, 2024

@ampandres It's not accurate to call it the same problem without seeing the error message. 😉

You don't provide the error message. I guess your issue is the same as Azure/azure-cli-extensions#8264. I've reported to rdbms-connect owner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Service Attention This issue is responsible by Azure service team. Similar-Issue
Projects
None yet
Development

No branches or pull requests

4 participants