[BUG] ScalableCluster Deployment Fails when Physical Network Adapters are already in a Team for VSwitch

[K3nks]

Describe the bug
Deployment fails with network validation issues. Deployment appears to be using method to pull physical network adapters that are in an Up state only.

To Reproduce
Steps to reproduce the behavior:

1. Have two Physical Network Adapters in a Team
2. Created External VSwitch in Hyper-V based on the Team
3. Attempt to create deployment specifying

• VSwitch.Name = "Name of the Virtual Switch e.g VM Switch"
• VSwitch.Adaptername = "Name of the Virtual Switch Adapter e.g Hyper-V Virtual Ethernet Adapter"
• Machines.NetworkConnection.AdapterName = "Name of the Virtual Switch Adapter"

Expected behavior
Use an existing external VM Switch which is based of a Team shouldn't throw an error and validate it based on ALL adapters available, not just physical ones

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

Environment (please complete the following information):

• AKS Edge Essentials Version 1.9.262.0
• Kubernetes version K3s
• Windows Host OS (please complete the following information):
  • Edition: Windows Server Standard 2019
  • Version: 10.0.17763.6659
  • Virtual Machine: Hyper-V

Additional context
Add any other context about the problem here.

[K3nks]

The deployment works for SingleMachineCluster as you don't have to specify the values for

• VSwitch.Name = "Name of the Virtual Switch e.g VM Switch"
• VSwitch.Adaptername = "Name of the Virtual Switch Adapter e.g Hyper-V Virtual Ethernet Adapter"
• Machines.NetworkConnection.AdapterName = "Name of the Virtual Switch Adapter"

Appears to be an issue with the logic for the test of the Net adapters

[K3nks]

Result is still the same with LBFO or SET Teaming used by the host for creation of the vSwitch

[parameshbabu]

The product doesn't support teamed network adapters today. We will look into this further to see how we can enable this.