az extension add --name azure-firewall #30594
Assignees
Labels
Azure CLI Team
The command of the issue is owned by Azure CLI team
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Network
az network vnet/lb/nic/dns/etc...
Possible-Solution
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Similar-Issue
Milestone
Comments
|
Thank you for opening this issue, we will look into it. |
microsoft-github-policy-service
bot
added
the
customer-reported
yonzhan
added
the
Azure CLI Team
yonzhan
added
Network
|
@Vijayraghul87 what exactly is your error (message)? |
|
@necusjz az extension add --name azure-firewall |
|
Here are some similar issues that might help you. Please check if they can solve your problem.
Possible solution (Extracted from existing issue, might be incorrect; please verify carefully) Solution 1:Please try the following action plan:
Reference: Solution 2:Try running the following command to manually install the extension: This command does the same thing as Reference: |
|
This issue also happens with Does not work on 2.66.0 and 2.67.0. Works on 2.65.0. v2.67.0 Stdout logsThe problem seems to be that the CPython interpreter ( v2.67.0 LogsLast good version: v2.65.0v2.65.0 stdout logsv2.65.0 logs |
|
@0x326 and @Vijayraghul87 , we tried |
|
@AllyW, I upgraded from version Also installing a new extensions fails with the same error message. According to you question, I got the following result. Using a slightly different command aborts with The full output is already documented at comment. |
|
@0x326 Thanks for the log. I see What's the version of this Python? Previously, I met an issue that 3.12.6's module is not compatible with 3.12.7. I assume the Python you installed is interfere with CLI's bundled Python. Here is the ultimate solution for this: #29630 (comment) |
orgads
added a commit
to orgads/azure-cli
that referenced
this issue
Feb 10, 2025
The scripts are installed in <base>/Scripts, but PYTHONPATH was set to <scripts>/src, although this directory doesn't even exist. I guess the deployment used to be in src, but this is no longer the case. Setting PYTHONPATH is done to avoid conflicts with other installations of Python on the same machine. When it is set incorrectly, Python tend to crash on startup (typically when loading incompatible ctypes). Fixes Azure#28004, Azure#29630, Azure#30517, Azure#30536, Azure#30594, Azure#30700, Azure#30792.
3 tasks
orgads
added a commit
to orgads/azure-cli
that referenced
this issue
Feb 10, 2025
The scripts are installed in <base>/Scripts, but PYTHONPATH was set to <scripts>/src, although this directory doesn't even exist. I guess the deployment used to be in src, but this is no longer the case. Setting PYTHONPATH is done to avoid conflicts with other installations of Python on the same machine. When it is set incorrectly Python tends to crash on startup (typically when loading incompatible ctypes). Fixes Azure#28004, Azure#29630, Azure#30517, Azure#30536, Azure#30594, Azure#30700, Azure#30792.
orgads
added a commit
to orgads/azure-cli
that referenced
this issue
Feb 12, 2025
The scripts are installed in <base>/Scripts, but PYTHONPATH was set to <scripts>/src, although this directory doesn't even exist. I guess the deployment used to be in src, but this is no longer the case. Setting PYTHONPATH is done to avoid conflicts with other installations of Python on the same machine. When it is set incorrectly Python tends to crash on startup (typically when loading incompatible ctypes). Fixes Azure#28004, Azure#29630, Azure#30517, Azure#30536, Azure#30594, Azure#30700, Azure#30792.
orgads
added a commit
to orgads/azure-cli
that referenced
this issue
Feb 12, 2025
Setting PYTHONPATH is done to avoid conflicts with other installations of Python on the same machine. When it is set incorrectly Python tends to crash on startup (typically when loading incompatible ctypes). There were old scripts in <base>/Scripts, which set PYTHONPATH so that Python prefers the bundled libs over the system ones. The problem with these scripts is that they set the wrong path. But these scripts no longer seem to be used. They were replaced by new ones in wbin. The problem with those is that PYTHONPATH was not set at all in them. Update the scripts to set PYTHONPATH correctly, both for bash and cmd. Fixes Azure#28004, Azure#29630, Azure#30517, Azure#30536, Azure#30594, Azure#30700, Azure#30792.
orgads
added a commit
to orgads/azure-cli
that referenced
this issue
Feb 17, 2025
Setting PYTHONPATH is done to avoid conflicts with other installations of Python on the same machine. When it is set incorrectly Python tends to crash on startup (typically when loading incompatible ctypes). There were old scripts in <base>/Scripts, which set PYTHONPATH so that Python prefers the bundled libs over the system ones. The problem with these scripts is that they set the wrong path. But these scripts no longer seem to be used. They were replaced by new ones in wbin. The problem with those is that PYTHONPATH was not set at all in them. Update the scripts to set PYTHONPATH correctly, both for bash and cmd. Fixes Azure#25067, Azure#28004, Azure#29630, Azure#30517, Azure#30536, Azure#30594, Azure#30700, Azure#30792.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az extension addErrors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az extension add --name {}Expected Behavior
Environment Summary
Additional Context
The text was updated successfully, but these errors were encountered: