-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Antrea Agent failing to start on Windows #3636
Comments
I created a brand new Windows Node and ran into the exact same issue again after following the steps in https://github.com/antrea-io/antrea/blob/main/docs/windows.md#installation-via-wins-docker-based-runtimes |
Hi @antoninbas , I saw the Windows Node network adapter name was "Ethernet" which was configured with NodeIP address, and there are exsiting netadapter named as "vEthernet (Ethernet)". The crash happens after creating HNSNetwork. By default, Windows host should create a new virtual management network adpater with a name format "vEthernet ($netadapter_name)", and we use this format to check the existence of the virtual management adapter after creating the HNSNetwork. In this testbed, the name is used by another adapter, but Antrea doesn't know it so uses a wrong name to continue the following steps, this generate the issues. I think a fix could be use the IP and MAC to find the virtual adapter instead of the name. |
@wenyingd Thanks for the quick reply. Your explanation makes sense. I ran some more experiments and it seems that this network adapter ( I am using an AWS AMI named Microsoft Windows Server 2019 Base with Containers which comes with Windows container support out-of-the-box. It seems that this support is based on Mirantis Container Runtime:
I haven't tried running Antrea on Windows in 1 year, so I think quite a lot of things have changed since then. It seems that the Mirantis Container Runtime may be responsible for creating this network adapter. Or maybe I am totally wrong :) But it seems that it would be a good idea not to assume that there is no existing adapter with the |
Describe the bug
I'm trying to run Antrea on a Windows Node, but the agents gets into a CrashLoopBackOff state, with the following error:
The error doesn't really help me troubleshoot anything.
Versions:
Antrea v1.6.0
Additional context:
I am using Docker as the container runtime, and using the antrea-windows DaemonSet to run the agent.
Here is some additional information:
The text was updated successfully, but these errors were encountered: