search

Azure / AKS

Azure Kubernetes Service
https://azure.github.io/AKS/
1.95k stars 305 forks source link

[BUG] AKS cluster can't recover after dev subscription re-enabled after hitting limit in previous month #3385

Open kamilon opened 1 year ago

kamilon commented 1 year ago

Describe the bug My developer subscription with a spending limit was disabled for hitting the limit. After the subscription reset and became re-enabled the AKS cluster has not been able to get the node pool healthy. I've even tried creating another pool. I'm able to use and create other resource types.

To Reproduce Steps to reproduce the behavior:

  1. Deploy AKS cluster in spending limited subscription
  2. Hit spending limit
  3. Wait for subscription spending limit to reset
  4. Repro

Expected behavior AKS either automatically or manually is able to be brought back to a healthy state after the subscription was re-enabled. I can't start or stop the AKS cluster, start, stop or restart the host pool or anything.

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

Additional context The message I get is: Failed to scale node pool 'xxx' in Kubernetes service 'xxx'. Error: autorest/azure: Service returned an error. Status=409 Code="SubscriptionNotRegistered" Message="Subscription is not registered."

ghost commented 1 year ago

Action required from @Azure/aks-pm

ghost commented 1 year ago

Issue needing attention of @Azure/aks-leads

kamilon commented 1 year ago

This has been sitting a while so I want to make sure it is known that this is still an issue. Assistance would be appreciated.

justindavies commented 1 year ago

Would you be able to check in your subscription via the portal that the ContainerService provider is registered on your subscription? It sounds like the registration has dropped off when your subscription was paused.

kamilon commented 1 year ago

I just confirmed it is registered.

kamilon commented 1 year ago

How do I escalate this issue? It's been months with no progress.

ghost commented 1 year ago

Action required from @Azure/aks-pm

ghost commented 1 year ago

Issue needing attention of @Azure/aks-leads

ghost commented 1 year ago

Issue needing attention of @Azure/aks-leads

ghost commented 1 year ago

Issue needing attention of @Azure/aks-leads

ghost commented 1 year ago

Issue needing attention of @Azure/aks-leads

ghost commented 1 year ago

Issue needing attention of @Azure/aks-leads

ghost commented 1 year ago

Issue needing attention of @Azure/aks-leads

ghost commented 1 year ago

Issue needing attention of @Azure/aks-leads

ghost commented 1 year ago

Issue needing attention of @Azure/aks-leads

AllenWen-at-Azure commented 6 days ago

Hi @kamilon are you still seeing this issue? If it is the case, please file a support ticket, support engineers need your environment information to further investigate the issue.

microsoft-github-policy-service[bot] commented 6 days ago

Hi there :wave: AKS bot here. This issue has been tagged as needing a support request so that the AKS support and engineering teams have a look into this particular cluster/issue.

Follow the steps here to create a support ticket for Azure Kubernetes Service and the cluster discussed in this issue.

Please do mention this issue in the case description so our teams can coordinate to help you.

Thank you!