yahoo-eng-team team mailing list archive

[Ivan Zhang <1956034@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The ovn octavia provider has added the support for health monitor in a commit one year ago:
https://opendev.org/openstack/ovn-octavia-provider/commit/8bbd8f1b62d7811433079bff8ce940fbdd041a0c

It reuse the OVN distributed DHCP
port(device_owner="network:distributed"), whose mac address is allocated
by neutron, but in the ovn's implementation, the health monitor message
will be sent from this ip with a different mac address obtained from
NB_Global table in northbound db. This breaks the ARP protocol and
metadata request to ovn metadata agent will timeout. A possible fix is
to use a different neutron port for the health monitor purpose.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: ovn-octavia-provider

** Tags added: ovn-octavia-provider

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

Title:
  ovn load balancer health monitor cause mac address conflict

Status in neutron:
  New

Bug description:
  The ovn octavia provider has added the support for health monitor in a commit one year ago:
  https://opendev.org/openstack/ovn-octavia-provider/commit/8bbd8f1b62d7811433079bff8ce940fbdd041a0c

  It reuse the OVN distributed DHCP
  port(device_owner="network:distributed"), whose mac address is
  allocated by neutron, but in the ovn's implementation, the health
  monitor message will be sent from this ip with a different mac address
  obtained from NB_Global table in northbound db. This breaks the ARP
  protocol and metadata request to ovn metadata agent will timeout. A
  possible fix is to use a different neutron port for the health monitor
  purpose.

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