Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 2160474

Summary: ovn ignores igmp v2 join request
Product: Red Hat Enterprise Linux Fast Datapath Reporter: Haresh Khandelwal <hakhande>
Component: ovn22.03Assignee: Dumitru Ceara <dceara>
Status: CLOSED NOTABUG QA Contact: ying xu <yinxu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: RHEL 8.0CC: ctrautma, dceara, jiji, jishi
Target Milestone: ---   
Target Release: ---   
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: 2023-01-16 12:46:36 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 Haresh Khandelwal 2023-01-12 14:37:33 UTC 
Description of problem:

Receiver sends igmpv2 join request but ovn does not register it. This leads igmpv2 based mutlicast useless. 

[root@testpmd-dpdk-dut ~]# cat /proc/sys/net/ipv4/conf/eth0/force_igmp_version 
3
[root@testpmd-dpdk-dut ~]# ip addr add 224.1.1.1/32 dev eth0 autojoin

[root@controller-0 /]# ovn-sbctl list IGMP_group
_uuid               : 2b5e92ad-d08d-48c5-afdb-036c69b172f5
address             : "224.1.1.1"
chassis             : 29767457-b129-4cf2-9d55-386211dd3a3a
datapath            : a81e6ee5-333f-4aad-b54e-3fe98e333d0e
ports               : [c9ab803f-b6a7-4eb7-8103-ee2326542170]
[root@controller-0 /]# 

Same does not work when force_igmp_version set to 2 which forces to send v2 join.

Version-Release number of selected component (if applicable):
ovn22.03-22.03.0

How reproducible:
Always

Steps to Reproduce:
1. See description
2.
3.

Actual results:
IGMPv2 join is not registered

Expected results:
IGMPv2 join should be registered

Additional info:
Comment 1 Dumitru Ceara 2023-01-13 13:29:34 UTC 
Can you please share the NB and the OVS database from the node where you're sending the igmp v2 report?

A quick test with upstream OVN:

$ ip netns exec vm2 cat /proc/sys/net/ipv4/conf/vm2/force_igmp_version 
2

$ ip netns exec vm2 ip addr add 224.1.1.1/32 dev vm2 autojoin

This generates a v2 report:

14:28:52.192785 00:00:00:00:00:02 > 01:00:5e:01:01:01, ethertype IPv4 (0x0800), length 46: (tos 0xc0, ttl 1, id 0, offset 0, flags [DF], proto IGMP (2), length 32, options (RA))                                                            
    42.42.42.3 > 224.1.1.1: igmp v2 report 224.1.1.1

And OVN learns it:
$ ovn-sbctl find igmp address=224.1.1.1
_uuid               : 6fa08a61-5f96-407a-8f98-fb794fc6505d
address             : "224.1.1.1"
chassis             : 6f2a8feb-e54f-41ca-a531-f722acc915de
datapath            : 57ea9e95-8e89-4c54-ac00-fd89f6810e2a
ports               : [8277afcb-a132-474a-9309-06ccd137b488]