The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.
Bug 1866820 - [OVN] With ovn-monitor-all=true, IGMP groups are flushed by ovn-controllers that don't own them.
Summary: [OVN] With ovn-monitor-all=true, IGMP groups are flushed by ovn-controllers t...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux Fast Datapath
Classification: Red Hat
Component: ovn2.13
Version: FDP 20.E
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Dumitru Ceara
QA Contact: ying xu
URL:
Whiteboard:
Depends On:
Blocks: 1843695
TreeView+ depends on / blocked
 
Reported: 2020-08-06 13:35 UTC by Dumitru Ceara
Modified: 2020-09-16 16:01 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1843695
Environment:
Last Closed: 2020-09-16 16:01:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:3769 0 None None None 2020-09-16 16:01:34 UTC

Comment 5 ying xu 2020-08-25 08:05:57 UTC
I talked with devel, this bug shows that the igmp group uuid is changing when set the config both the two chassis. 

# ovn-nbctl show
switch 27905ee2-17a1-46d7-8456-0022dd571e72 (ls)
    port vm1
        addresses: ["00:00:00:00:00:01"]
    port vm2
        addresses: ["00:00:00:00:00:02"]
    port vm3
        addresses: ["00:00:00:00:00:03"]

I reproduced this issue on versoion:
ovn2.13-20.06.1-6.el8fdp.x86_64


I join group 227.1.1.1,before set the  ovn-monitor-all=true
the igmp group is stable:
#ovn-sbctl list IGMP_group

_uuid               : b7514b52-6aa8-4a0c-8aaa-1cbbe4c0e1ff
address             : "227.1.1.1"
chassis             : 7f2a78ed-fdcd-4688-aec9-fbed58196b28
datapath            : b4143970-c438-4c19-8668-3fdd82abb0b8
ports               : [ce022aa7-508f-45a2-8ec0-e0b609182434]


#ovn-sbctl list IGMP_group
_uuid               : b7514b52-6aa8-4a0c-8aaa-1cbbe4c0e1ff    ----------the uuid is the same as last time
address             : "227.1.1.1"
chassis             : 7f2a78ed-fdcd-4688-aec9-fbed58196b28
datapath            : b4143970-c438-4c19-8668-3fdd82abb0b8
ports               : [ce022aa7-508f-45a2-8ec0-e0b609182434]

after se the ovn-monitor-all=true,the uuid is changing,and sometimes no group.

#ovn-sbctl list IGMP_group'

#ovn-sbctl list IGMP_group
_uuid               : 55d6fb85-e2c9-4914-a9a8-0168496cdcf8  -----------the uuid is different
address             : "227.1.1.1"
chassis             : 7f2a78ed-fdcd-4688-aec9-fbed58196b28
datapath            : b4143970-c438-4c19-8668-3fdd82abb0b8
ports               : [ce022aa7-508f-45a2-8ec0-e0b609182434]

#ovn-sbctl list IGMP_group   ------------sometimes no group show(when no group,traffic will be wrong forwarding)


verified on version:
# rpm -qa|grep ovn
ovn2.13-20.06.2-1.el8fdp.x86_64
ovn2.13-host-20.06.2-1.el8fdp.x86_64
ovn2.13-central-20.06.2-1.el8fdp.x86_64



before set the config on both chassis:
# ovn-sbctl list IGMP_group
_uuid               : abaa458c-e576-4c14-b6a0-1394296336a2
address             : "227.1.1.1"
chassis             : 68e93f3a-66e1-474d-850f-3e637496d6dd
datapath            : 5420d6a8-9e1f-4965-b2d2-bf964ce129c0
ports               : [692c8fd5-d936-4e24-a2db-0b2f4cb86437]

after set the config on both chassis:
# ovn-sbctl list IGMP_group
_uuid               : abaa458c-e576-4c14-b6a0-1394296336a2  -----------it is the same as before
address             : "227.1.1.1"
chassis             : 68e93f3a-66e1-474d-850f-3e637496d6dd
datapath            : 5420d6a8-9e1f-4965-b2d2-bf964ce129c0
ports               : [692c8fd5-d936-4e24-a2db-0b2f4cb86437]

of course the traffic are right now.

Comment 7 errata-xmlrpc 2020-09-16 16:01: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 (ovn2.13 bug fix and enhancement update), 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:3769


Note You need to log in before you can comment on or make changes to this bug.