[BUG] AKS installation stuck on "Validate KVA"

[arp-mbender]

[BUG] AKS installation stuck on "Validate KVA"

[arp-mbender]

@Elektronenvolt I had the EXACT same issue. Well, SR-IOV was supported, but it doesn't support MAC address spoofing (but there are no errors enabling this; it just doesn't work in the end).

[markamber]

I can reproduce this! On server 2019 clustered and 2022 standalone.

Looks like a bootstrap VM boots and gets its cloud config but then nothing happens. I was using static addresses , no VLAN, and static addresses yes VLAN.

Seems like it might just be broken

[arp-mbender]

@markamber Thanks for confirming.

Quite annoying, TBH. I keep trying to get some experience with Kubernetes by setting up a basic environment, and I keep hitting strange roadblocks. Processes that should automate this... don't work (like the one described here), while manual attempts at setting things up fail due to versioning issues between some tutorial and my own environment...

[abhilashaagarwala]

@SummerSmith @walterov FYI

[Elektronenvolt]

I've noticed the same thing on one of our setups. The validation reports an issue at KVA - a VM gets created but it's not reachable by ssh, e.g. But - I'm not sure if it's a bug or the validation checks are just doing their job!

Its only one machine where it fails, no problems on many other machines. We didn't find the root cause so far, but we focus on the Hyper-V virtual switch / network card settings. I was not able to ping the VM created by KVA validation check - what usually works.

@arp-mbender @markamber - try to create a custom VM with the same virtual switch you use for AKS Hybrid and check if you get connectivity. May you have an issue on the virtual switch

At PowerShell it looks like this:

[arp-mbender]

Aye, it turned out to be a connectivity issue. I'm not sure how I missed it. :(

[Elektronenvolt]

@arp-mbender in our case it was a network card not supporting SR-IOV, Virtual Machine Queues, e.g. Replaced it now with a "Hyper-V certified" card.