Bug 1445501

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, hongli, smunilla
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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:
: 1445502 (view as bug list) Environment:
Last Closed: 2017-08-10 05:21:25 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: 1445502    

Description Ben Bennett 2017-04-25 19:54:17 UTC
Description of problem:

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


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

3.5.0

How reproducible:

Always

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-06-05 07:27:34 UTC
verified in atomic-openshift-3.6.94-1.git.0.ba4aad2.el7.x86_64 and the issue has been fixed.

Comment 4 errata-xmlrpc 2017-08-10 05:21:25 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/RHEA-2017:1716