Bug 1419652

Summary:	Multicast should be supported in vnid 0
Product:	OpenShift Container Platform	Reporter:	Weibin Liang <weliang>
Component:	Networking	Assignee:	Dan Winship <danw>
Status:	CLOSED ERRATA	QA Contact:	Meng Bo <bmeng>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.5.0	CC:	aloughla, aos-bugs, bbennett, tdawson
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-04-12 19:11:50 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:

Description Weibin Liang 2017-02-06 16:26:47 UTC

Description of problem:
Pods in the admin tenant (default project) should be able to send/receive multicast traffic from other admin tenant pods, bu in latest 3.5 code, multicast does not work in vnid 0

Version-Release number of selected component (if applicable):
oc v3.5.0.16+a26133a
kubernetes v1.5.2+43a9be4
openshift v3.5.0.16+a26133a
kubernetes v1.5.2+43a9be4

How reproducible:
Every time.

Steps to Reproduce:
1. oc project default
2. oc annotate netnamespace default netnamespace.network.openshift.io/multicast-enabled=true
3. oc create -f https://raw.githubusercontent.com/weliang1/Openshift_Networking/master/OSE3.3/multicast.json
4. oc rsh hello-pod-1
   iperf -c 232.43.211.234 -u -T 32 -t 3000 -i 1
5. oc rsh hello-pod-2
   iperf -s -u -B 232.43.211.234  -i 1



Actual results:
hello-pod-2 does not receive multicast traffic sent from hello-pod-1

Expected results:
hello-pod-2 should receive multicast traffic sent from hello-pod-1

Additional info:

Comment 1 Troy Dawson 2017-02-08 22:28:08 UTC

This has been merged into ocp and is in OCP v3.5.0.18 or newer.

Comment 3 Weibin Liang 2017-02-09 15:57:22 UTC

Test case passed in oc v3.5.0.18+9a5d1aa

Comment 5 errata-xmlrpc 2017-04-12 19:11:50 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-2017:0884