Bug 1445502

Summary: On a single-node cluster, multicast is never correctly set up.
Product: OpenShift Container Platform Reporter: Ben Bennett <bbennett>
Component: NetworkingAssignee: Ben Bennett <bbennett>
Status: CLOSED ERRATA QA Contact: Meng Bo <bmeng>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: aos-bugs, bmeng, hongli, smunilla
Target Milestone: ---   
Target Release: 3.5.z   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: The code to set up multicast was not run when only one node was in the cluster. Consequence: Multicast traffic was dropped when on a single-node cluster. Fix: Change the rules so the multicast setup is performed for a single-node. Result: Multicast works for single-node clusters.
Story Points: ---
Clone Of: 1445501 Environment:
Last Closed: 2017-05-18 09:28: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:
Bug Depends On: 1445501    
Bug Blocks:    

Description Ben Bennett 2017-04-25 19:58:32 UTC
+++ This bug was initially created as a clone of Bug #1445501 +++

Description of problem:

On a single-node cluster, multicast packets are not delivered.

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


How reproducible:


Steps to Reproduce:
1. Create a single node cluster
2. Create a pod to receive multicast packets
3. Create a pod to send multicast packets
4. Watch for multicast delivery

Actual results:

At step 4, no packets are delivered.

Expected results:

At step 4, packets should be delivered.

Additional info:

Comment 2 Hongan Li 2017-04-28 07:33:20 UTC
verified in atomic-openshift- and the bug has been fixed. Multicast works well on single node cluster.

# ovs-ofctl dump-flows br0 -O openflow13 | grep table=111
 cookie=0x0, duration=7463.021s, table=111, n_packets=78, n_bytes=7062, priority=100 actions=goto_table:120

Comment 4 errata-xmlrpc 2017-05-18 09:28: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.