-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.12.z
-
Moderate
-
No
-
False
-
Description of problem:
Adding Windows node to 4.12.33 cluster using Windows Server 2019, version 1809 which is a supported one as per official documentation. The node is getting added to the cluster but is in notready state.
The kubelet.logs shows the error message: Failed to fetch current HNS endpoints" err="failed during hnsCallRawResponse: hnsCall failed in Win32: The specified module could not be found. (0x7e)"
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
The network issue (not assigning a specific IP) has been resolved by the single NIC usage on the Windows node (as we do not support dual NIC). -->The SSH key has been configured correct as we are able to access the node. --> Node joins the cluster as we can see in the `oc get nodes` command. --> But node shows the NotReady state.
Logs attached here: https://drive.google.com/drive/folders/1QUZvrZi66J3ux3yBFVB5OfmPwMniLecy?usp=drive_link
Case ID: 03616994