AKS icon indicating copy to clipboard operation
AKS copied to clipboard
verified publisher icon Azure

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

Open kamilon opened this issue 3 years ago • 22 comments

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):

  • CLI Version N\A
  • Kubernetes version 1.22.1
  • Browser Edge/Chrome

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."

kamilon avatar Dec 09 '22 06:12 kamilon

Action required from @Azure/aks-pm

ghost avatar Jan 08 '23 16:01 ghost

Issue needing attention of @Azure/aks-leads

ghost avatar Jan 23 '23 18:01 ghost

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.

kamilon avatar Jan 24 '23 17:01 kamilon

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.

justindavies avatar Feb 03 '23 19:02 justindavies

I just confirmed it is registered.

kamilon avatar Feb 09 '23 21:02 kamilon

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

kamilon avatar Mar 03 '23 21:03 kamilon

Action required from @Azure/aks-pm

ghost avatar Apr 03 '23 01:04 ghost

Issue needing attention of @Azure/aks-leads

ghost avatar Apr 18 '23 18:04 ghost

Issue needing attention of @Azure/aks-leads

ghost avatar May 04 '23 00:05 ghost

Issue needing attention of @Azure/aks-leads

ghost avatar May 19 '23 06:05 ghost

Issue needing attention of @Azure/aks-leads

ghost avatar Jun 03 '23 12:06 ghost

Issue needing attention of @Azure/aks-leads

ghost avatar Jun 18 '23 18:06 ghost

Issue needing attention of @Azure/aks-leads

ghost avatar Jul 04 '23 00:07 ghost

Issue needing attention of @Azure/aks-leads

ghost avatar Jul 19 '23 06:07 ghost

Issue needing attention of @Azure/aks-leads

ghost avatar Aug 03 '23 12:08 ghost

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.

AllenWen-at-Azure avatar Sep 11 '24 14:09 AllenWen-at-Azure

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!

microsoft-github-policy-service[bot] avatar Sep 11 '24 14:09 microsoft-github-policy-service[bot]