yahoo-eng-team team mailing list archive

[Lucas Alvares Gomes <1933207@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=1949460

VMs subscribed to a multicast group are receiving 2 multicast packets
when only one is sent by a sender VM.

I dug into the problem and found out that the problematic option is
"mcast_flood" set in the localnet port types (provider network port) by
ML2/OVN. Setting it to "false" fix the duplication problem.

The QE team upstream ran our downstream tests against an environment
with that option disabled and everything worked fine. I think we should
fix it upstream as well.

Note, the problematic option is the "mcast_flood". A similar option
called "mcast_flood_reports" should still be enabled.

** Affects: neutron
     Importance: Medium
     Assignee: Lucas Alvares Gomes (lucasagomes)
         Status: Confirmed

** Changed in: neutron
     Assignee: (unassigned) => Lucas Alvares Gomes (lucasagomes)

** Changed in: neutron
       Status: New => Confirmed

** Changed in: neutron
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1933207

Title:
  [OVN] Duplicated multicast packets on external network

Status in neutron:
  Confirmed

Bug description:
  Reported at: https://bugzilla.redhat.com/show_bug.cgi?id=1949460

  VMs subscribed to a multicast group are receiving 2 multicast packets
  when only one is sent by a sender VM.

  I dug into the problem and found out that the problematic option is
  "mcast_flood" set in the localnet port types (provider network port)
  by ML2/OVN. Setting it to "false" fix the duplication problem.

  The QE team upstream ran our downstream tests against an environment
  with that option disabled and everything worked fine. I think we
  should fix it upstream as well.

  Note, the problematic option is the "mcast_flood". A similar option
  called "mcast_flood_reports" should still be enabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1933207/+subscriptions