-
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
azure cli latest version fails with az aks create command #20401
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/aks-pm. Issue DetailsThis is autogenerated. Please review and update as needed.Describe the bugCommand Name Errors:
To Reproduce:Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
Expected BehaviorEnvironment Summary
Additional Context
|
route to service team |
If possible to expedite, as it is blocker for me and I have series of
workshops lined up next week on AKS and Arc on AKS.
For both we are heavily dependent on AZ CLI.
Thanks in advance!
…On Thu, Nov 18, 2021 at 4:31 AM yonzhan ***@***.***> wrote:
route to service team
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20401 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASI6PXQTZ3IZOVRI6ZBZNDUMQX4NANCNFSM5IH7EE2A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Monojit Datta
Mob1:9831445901 | Mob2:9903935901
B: https://monojitd.codemongers.net/ <https://codemongers.wordpress.com/>
G: https://github.com/monojit18
L: https://www.linkedin.com/in/monojit-datta/
|
Same error here for another |
Yes true, same error.
Actually this is a bigger problem....I can create the cluster from Portal
also, but how to do this context switch :(
Surprisingly, things are working from Azure CLoud Shell, till now!
…On Thu, Nov 18, 2021 at 3:14 PM Stephen Pope ***@***.***> wrote:
Same error here for another aks command: #20410
<#20410>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20401 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASI6PQ635NSNWAFYZLI4HLUMTDIHANCNFSM5IH7EE2A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Monojit Datta
Mob1:9831445901 | Mob2:9903935901
B: https://monojitd.codemongers.net/ <https://codemongers.wordpress.com/>
G: https://github.com/monojit18
L: https://www.linkedin.com/in/monojit-datta/
|
Edit /usr/local/Cellar/azure-cli/2.30.0_1/libexec/lib/python3.10/site-packages/tabulate.py |
Sorry for the inconvenience. From the error message, the error is caused by the incompatibility between
Please consider the following workaround, otherwise, please use cloudshell from portal or wait for the next release to fix this issue. |
Duplicate of #20348 |
This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks create
Errors:
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
az aks create --name {} --resource-group {} --kubernetes-version {} --location {} --vnet-subnet-id {} --enable-addons {} --service-cidr {} --dns-service-ip {} --node-vm-size {} --node-count {} --max-pods {} --service-principal {} --client-secret {} --network-plugin {} --network-policy {} --nodepool-name {} --vm-set-type {} --generate-ssh-keys --enable-aad --aad-admin-group-object-ids {} --aad-tenant-id {} --attach-acr {} --workspace-resource-id {} --dns-name-prefix {}
Expected Behavior
Environment Summary
Additional Context
The text was updated successfully, but these errors were encountered: