Azure / aksArc

# Welcome to the Azure Kubernetes Service on Azure Stack HCI repo This is where the AKS-HCI team will track features and issues with AKS-HCI. We will monitor this repo in order to engage with our community and discuss questions, customer scenarios, or feature requests. Checkout our projects tab to see the roadmap for AKS-HCI!
MIT License
109 stars 45 forks source link

[BUG] AKS installation via WAC fails on "Validate KVA" validation step #374

Closed verifiedtomic closed 4 weeks ago

verifiedtomic commented 4 weeks ago

Describe the bug Cluster validation fails (timeouts) on the last validation step - Validate KVA with network connectivity error - Temporary failure in name resolution. AKSHCI network and internet connectivity validation failed: http-connectivity-test-aks-hci.

To Reproduce Steps to reproduce the behavior: Configure basic AKS Hybrid via WAC Wizard in nested virtualization by following below wizard config.

Expected behavior All validations complete successfully and New Cluster step becomes available in WAC AKS Wizard

Environment (please complete the following information):

Additional context Wizard Config in lab environment (nested virtualization) Static IP address allocation method System checks Windows Admin Center is connected to Azure: Connected Roles & features to install: Hyper-V, Hyper-V-PowerShell Firewall ports to open: 45000, 45001, 55000, 65000 Host configuration Management cluster name: az-mon-poc-aks Folder to store VM images: C: Virtual network name: aks-default-network Internet-connected virtual switch: vSW-AKS VLAN ID: 0 IP address allocation method: Static (Recommended) Subnet prefix: 10.10.2.0/22 Gateway: 10.10.1.1 DNS servers: 8.8.8.8,1.1.1.1,10.10.1.10 Virtual IP pool start: 10.10.2.101 Virtual IP pool end: 10.10.2.200 Kubernetes node IP pool start: 10.10.2.10 Kubernetes node IP pool end: 10.10.2.100 MAC address allocation: Automatic Azure registration Azure subscription: Azure subscription 1 Resource group: rg-euwe-aks-hybrid

Wizard Config in lab environment (nested virtualization) DHCP IP address allocation method Windows Admin Center is connected to Azure: Connected Roles & features to install Hyper-V, Hyper-V-PowerShell Firewall ports to open: 45000, 45001, 55000, 65000 Host configuration Management cluster name: aks-management-cluster-1 Folder to store VM images: C: Virtual network name:aks-default-network Internet-connected virtual switch: vSW-AKS VLAN ID: 0 IP address allocation method: DHCP Virtual IP pool start: 10.10.2.10 Virtual IP pool end: 10.10.2.101 MAC address allocation: Automatic Azure registration Azure subscription: Azure subscription 1 Resource group: rg-euwe-aks-hybrid

image

This issue is simmilar to [BUG] AKS installation stuck on "Validate KVA" #363, but here the wizard fails to create a KVA.

Collect log files

TestName | Category | TestResult | Details | Recommendation -- | -- | -- | -- | -- Validate KVA | KVA | Failed | C:\Program Files\AksHci\kvactl.exe validate --configfile "C:\AksHCI\1.0.22.10209\yaml\appliance.yaml" --provider=azurestackhci --enable-canary-diagnostics System.Collections.Hashtable.generic_non_zero 1 [Error: { "code": "CanaryDiagnosticsError", "message": "{\n \"code\": \"GuestInternetConnectivityError\",\n \"message\": \"Not able to connect to https://mcr.microsoft.com. Error returned: action failed after 3 attempts: Get \\\"https://mcr.microsoft.com\\\": dial tcp: lookup mcr.microsoft.com: Temporary failure in name resolution. AKSHCI network and internet connectivity validation failed: http-connectivity-test-aks-hci. 1. Please check your networking setup and ensure the URLs mentioned in : https://learn.microsoft.com/en-us/azure/aks/hybrid/system-requirements?tabs=allow-table#network-port-and-url-requirements are reachable from the Appliance VM. 2. Check firewall/proxy settings\"\n }" }]

I can connect to https://mcr.microsoft.com via Edge browser from Host machine normally.

I'm new to K8 so probably something silly or is-well-known-but-I-don't-know is written in the explanation - please take that in mind. :)

Please let me know if you require any additional information.

Thanks!

verifiedtomic commented 4 weeks ago

It was a networking issue. Second try with DHCP option passed the validation