-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Closed
Labels
AKSaz aks/acs/openshiftaz aks/acs/openshiftService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.
Description
The AZ CLI was working alright, but when working on some of the AKS CLI commands, and started showing error below error and cannot be able to fix by trying re-installing.
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks get-credentials
Errors:
No module named 'azure.cli.core.azclierror'
Traceback (most recent call last):
pip-install-mjd5h3hf\knack\knack\cli.py, ln 206, in invoke
cli\core\commands\__init__.py, ln 523, in execute
azure\cli\core\__init__.py, ln 293, in load_arguments
cli\core\commands\__init__.py, ln 291, in load_arguments
pip-install-mjd5h3hf\knack\knack\commands.py, ln 97, in load_arguments
azure\cli\core\__init__.py, ln 490, in default_arguments_loader
...
<frozen importlib._bootstrap>, ln 219, in _call_with_frames_removed
cliextensions\aks-preview\azext_aks_preview\custom.py, ln 46, in <module>
from azure.cli.core.azclierror import ManualInterrupt, InvalidArgumentValueError, UnclassifiedUserFault, CLIInternalError, FileOperationError, ClientRequestError, DeploymentError, ValidationError, ArgumentUsageError, MutuallyExclusiveArgumentError, RequiredArgumentMissingError, ResourceNotFoundError
ModuleNotFoundError: No module named 'azure.cli.core.azclierror'
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- Put any pre-requisite steps here...
az aks get-credentials --resource-group {} --name {} --admin
Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.6.6
Shell: powershell.exe
azure-cli 2.0.77
Extensions:
aks-preview 0.5.19
Additional Context
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
AKSaz aks/acs/openshiftaz aks/acs/openshiftService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.