Azure / Azure/aksArc

[BUG] AKS cluster creation hangs when HCI node is in maintenance mode

Open
#315 0 comments 1 reaction 0 assignees View on GitHub
Bug
Dominant language
PowerShell
Stars
118
Forks
63
PR merge metrics
No merged PRs in 30d

Description

**Describe the bug**
Tested with 2 2-node Azure Stack HCI clusters:

When one of the Azure Stack HCI nodes is in Failover Cluster Maintenance Mode, the cluster of the control-plane or load-balancer VM hangs in the cluster, the VM will not boot and stays offline in Hyper-V. This causes the cluster creation process to hang.

**To Reproduce**
Steps to reproduce the behavior:
1. Set one node in maintenance mode
2. Create a new cluster

**Expected behavior**
AKS cluster creation succeeds

**Screenshots**
![image](https://user-images.githubusercontent.com/11892641/229603065-d741e884-bac7-464b-a75f-59dbd1c52b6b.png)
![image](https://user-images.githubusercontent.com/11892641/229603370-ab342b4d-6e77-4ca3-9da0-b10cc0fac677.png)

**Environment (please complete the following information):**
- OS: Azure Stack HCI - 10.0.25217
- AKS-HCI Powershell module version - 1.1.66
- AKS-HCI Version - 1.0.17.10310
- Kubernetes Version - v1.24.9 (if it succeeds)
-

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.