Closed hwdef closed 2 years ago
@hwdef thanks for reporting. @wenyingd @XinShuYang could you check the issue?
Hi @hwdef could you help provide ovs version?
ovs version is 2.15.3 download from https://downloads.antrea.io/ovs/ovs-2.15.3-antrea.0-win64.zip I guess it is a problem with the adaptation of windows server 2022, because I tested it on windows server 2019 and it is no problem.
ovs version is 2.15.3 download from https://downloads.antrea.io/ovs/ovs-2.15.3-antrea.0-win64.zip I guess it is a problem with the adaptation of windows server 2022, because I tested it on windows server 2019 and it is no problem.
May I know how did you run the powershell script "install_ovs.ps1"? By running ps script on a ssh connection or on a RDP connection? Please ensure to run it on a RDP (Remote desktop) connection or using console directly. I used to hit similar issues on a ssh connection because the path in the script is possible to be resolved as a wrong path on a ssh connection.
yes, I run the powershell on a RDP connection. The service registration is successful, but it cannot be started
Please help show the result of command "pnputil.exe -e".
Besides, could you try to run this command in powershell directly "C:\openvswitch\usr\sbin\ovsdb-server.exe C:\openvswitch\etc\openvswitch\conf.db -vfile:info --remote=punix:db.sock --remote=ptcp:6640 --log-file --pidfile", and paste the output here
PS C:\Users\Administrator> pnputil.exe -e
Microsoft PnP Utility
Published name : oem3.inf
Driver package provider : INTEL
Class : System devices
Driver date and version : 07/18/1968 10.1.11.4
Signer name : Microsoft Windows Hardware Compatibility Publisher
Published name : oem4.inf
Driver package provider : INTEL
Class : System devices
Driver date and version : 07/18/1968 10.1.11.4
Signer name : Microsoft Windows Hardware Compatibility Publisher
Published name : oem5.inf
Driver package provider : INTEL
Class : System devices
Driver date and version : 07/18/1968 10.1.11.4
Signer name : Microsoft Windows Hardware Compatibility Publisher
Published name : oem6.inf
Driver package provider : Marvell
Class : Network adapters
Driver date and version : 07/05/2021 3.1.3.0
Signer name : Microsoft Windows Hardware Compatibility Publisher
Published name : oem7.inf
Driver package provider : Intel
Class : Network adapters
Driver date and version : 06/22/2021 12.19.1.37
Signer name : Microsoft Windows Hardware Compatibility Publisher
Published name : oem2.inf
Driver package provider : ASIX
Class : Network adapters
Driver date and version : 11/09/2021 2.22.2.0
Signer name : Microsoft Windows Hardware Compatibility Publisher
Published name : oem9.inf
Driver package provider : NVIDIA Corporation
Class : Sound, video and game controllers
Driver date and version : 01/02/2022 1.3.39.3
Signer name : Microsoft Windows Hardware Compatibility Publisher
Published name : oem8.inf
Driver package provider : NVIDIA
Class : Display adapters
Driver date and version : 03/17/2022 30.0.15.1215
Signer name : Microsoft Windows Hardware Compatibility Publisher
Published name : oem11.inf
Driver package provider : The Linux Foundation (R)
Class : Network Service
Driver date and version : 10/13/2021 2.15.2.0
Signer name : WDKTestCert appveyor,132785990465004813
Published name : oem10.inf
Driver package provider : The Linux Foundation (R)
Class : Network Service
Driver date and version : 07/30/2021 2.14.2.0
Signer name : WDKTestCert appveyor,132720997603577275
Published name : oem12.inf
Driver package provider : The Linux Foundation (R)
Class : Network Service
Driver date and version : 11/19/2021 2.15.3.0
Signer name : WDKTestCert appveyor,132817604335078165
Published name : oem1.inf
Driver package provider : Microsoft
Class : Printers
Driver date and version : 06/21/2006 10.0.20348.1
Signer name : Microsoft Windows
Published name : oem0.inf
Driver package provider : Microsoft
Class : Printers
Driver date and version : 06/21/2006 10.0.20348.1
Signer name : Microsoft Windows
Please try to re-install OVS first. The steps include:
We tried to install OVS on Server 2022, and succeeded.
We tried to install OVS on Server 2022, and succeeded.
I followed the instructions above to reinstall once, and it still failed, The error message is the same as before. Now that you have successfully tested, I think this is a problem with my environment, I will continue to investigate, thank you for your help.
All executables have no output, is this normal?
@wenyingd @XinShuYang
Maybe this is the reason
I finally confirmed that the issues were caused by missing the three dll above. The reason for the lack is that these three dll are brought when installing docker, and I am using containerd.
By the way, docker has been deprecated in k8s 1.24, should the ovs installation script be equipped with containerd?
Describe the bug
can not install ovs in windows use
https://github.com/antrea-io/antrea/blob/main/hack/windows/Install-OVS.ps1
shell.To Reproduce
Expected
successfully installed
Actual behavior
Versions:
kubernetes version: 1.21.11 windows version: windows server 2022 container runtime: containerd
Additional context