[BUG] Newly created resources are not returned by the list API, but are returned by the listByResourceGroup API about azure-rest-api-specs HOT 5 OPEN

Hi @FumingZhang

This latency happens every time we create kubernetes clusters. (This also happens when creating other resources but it is more pronounced for Kubernetes clusters)

Here are the stats from tests carried out today:

Subscription ID: 1bdc0343-1eb7-49e6-b986-5dd354002cc7

First cluster

Cluster-name: kub-efossombe-test-001
Region: eastus
Create request time: 13:14:30 UTC
Available in ListByResource Group API time: 13:15:10 UTC (time spend: few seconds)
Available in List API time: 13:29:07 UTC (time spend: ~15min)

Second cluster

Cluster-name: kub-efossombe-test-002
Region: australiaeast
Create request time: 13:14:30 UTC
Available in ListByResource Group API time: 13:15:10 UTC (time spend: few seconds)
Available in List API time: 13:29:07 UTC (time spend: ~15min)

from azure-rest-api-specs.

@FumingZhang Please help have a look, thank you.

from azure-rest-api-specs.

Let us know if you need anything more from our side.

from azure-rest-api-specs.

@juniormbe, @fyrnaga, could you please provide more details about

• when did the issue occur?
• which subscription did you use?

This seems to be an anomaly in server-side. If it is not related to the SDK, please open a support ticket to the AKS team and you could share more details there.

BTW, I tried to make a repro (with python SDK & azure-cli), both list by sub and by resource group works fine.

from azure-rest-api-specs.

Thanks for sharing the details. I checked the log and found a very strange thing. During the period from 2024-04-10 13:15:00 to 2024-04-10 13:28:00, ARM received 164 list by sub requests and all ends with success, but there is no record on the AKS side during this period. From a behavioral point of view, it seems that ARM returns an empty result for AKS. To further investigate the cause, please open a support ticket.

from azure-rest-api-specs.