Open svollath opened 3 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/aks-pm.
Author: | svollath |
---|---|
Assignees: | - |
Labels: | `AKS`, `Service Attention` |
Milestone: | - |
route to service team
This is something I am struggling too. Even waiting too many 20mins didn't work.
% az network nsg list -o table | grep MC_cluster-ylz-test_cluster-ylz-test_eastus
eastus aks-agentpool-10899641-nsg Succeeded MC_cluster-ylz-test_cluster-ylz-test_eastus 1627be58-e4ec-462d-ab4f-4642af60fc63
% az network nsg list -g MC_cluster-ylz-test_cluster-ylz-test_eastus
[]
Describe the bug Sometimes, the commands for listing VNETs and NSGs return empty for up to 20min. after (aks automatic) creation, if
--resource-group
is used - at the same time the respective resources are included (with the correct resource-group) listed within all VNET resources, e.g. with justaz network vnet list
oraz network nsg list
To Reproduce
az aks create
az aks get-credentials
az network nsg list --resource-group=$AZ_MC_RG_NAME
... just works without
-g
option.... and this can succeed right away, but often takes between 10-20min., until the correct content is shown, like above.
Expected behavior automatically created VNET or NSG get listed for the given MC_Resource-Group, e.g.
aks-agentpool-12345678-nsg
when they are availableEnvironment summary azure-cli-2.26.1-1.el7.x86_64 on openSUSE Leap 15.3