Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1771083

Summary: Failed to bootstrap window node on OVNKubernetes cluster
Product: OpenShift Container Platform Reporter: Anurag saxena <anusaxen>
Component: NetworkingAssignee: Jacob Tanenbaum <jtanenba>
Networking sub component: ovn-kubernetes QA Contact: zhaozhanqi <zzhao>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: high    
Priority: high CC: aravindh, jtanenba, mifiedle, nagrawal, rbrattai, zzhao
Version: 4.3.0Keywords: TestBlocker
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-25 14:26:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1772900    
Bug Blocks:    
Attachments:
Description Flags
Screenshoft on windows node none

Description Anurag saxena 2019-11-11 20:45:11 UTC
Created attachment 1635003 [details]
Screenshoft on windows node

Description of problem: Kubelet service is not getting started on windows node. 

My clipboard from rdp doesn't seem to work so attaching the screenshot of stack trace with this bug.

Version-Release number of selected component (if applicable): Window node is on 
Windows Server 2019 Datacenter with containers image

How reproducible:Always


Steps to Reproduce:
1.Create a window instance in Azure and try to bootstrap it on existing linux nodes cluster
2.
3.

Actual results: Bootstrapping failed


Expected results: Expecting a successful bootstrap


Additional info:

Comment 3 Anurag saxena 2019-11-15 18:48:52 UTC
Thanks Aravindh. That might be the case. Will keep an eye on that

Comment 6 Anurag saxena 2019-11-25 00:55:09 UTC
This bug can be closed as we are now able to bootstrap win node, thanks to above 2 PRs. 
But now we are stuck at kubelet NotReady issue on Windows node being tracked here https://bugzilla.redhat.com/show_bug.cgi?id=1776048