Bug 1827391

Summary:	communication between pods on linux and windows nodes fail
Product:	OpenShift Container Platform	Reporter:	Jacob Tanenbaum <jtanenba>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Networking sub component:	ovn-kubernetes	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	urgent	CC:	anusaxen, dcbw, sttts, xtian
Version:	4.4
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1827392 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:30:55 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:
Bug Blocks:	1827392

Description Jacob Tanenbaum 2020-04-23 19:30:39 UTC

Description of problem:

Linux and windows pods cannot communicate with each other

Version-Release number of selected component (if applicable):


How reproducible:

everytime 


Steps to Reproduce:
1. deploy an openshift cluster with hybrid networking 
2. deploy a windows node 
3. deploy a webserver pod on the windows node 
4. deploy a client pod on a linux node 
5. attempt to network communication between the pods on the windows and linux nodes

Actual results:
traffic does not get routed between the windows and linux pods

Expected results:
traffic can flow from the windows and linux pods 


Additional info:

Comment 1 Jacob Tanenbaum 2020-04-23 19:35:50 UTC

along with https://github.com/openshift/cluster-network-operator/pull/604 should fully fix current windows networking issues

Comment 2 zhaozhanqi 2020-04-24 03:06:17 UTC

move the status to 'post' for now since the PR still in open

Comment 6 Dan Williams 2020-04-24 14:16:56 UTC

If you run a couple pods on the node, then "oc rsh" to the ovnkube-node pod, then "ovs-ofctl dump-flows br-ext" and all local pods have a flow in table=10 we're good.

Comment 8 errata-xmlrpc 2020-07-13 17:30:55 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409