yahoo-eng-team team mailing list archive

[Luis Tomas <2025637@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When a member of a loadbalancer has a FIP, it gets centralized (mac info
removed from NAT table) due to requirements on OVN side. When a member
gets deleted from a loadbalancer, the mac information gets updated in
the NAT table and the traffic to the FIP gets distributed again.
However, if the whole loadbalancer gets deleted with the cascade option,
the traffic to the member FIP is left centralized (without the NAT table
being updated with the MAC again)

** Affects: neutron
     Importance: Undecided
     Assignee: Luis Tomas (luis5tb)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => Luis Tomas (luis5tb)

** Changed in: neutron
       Status: New => In Progress

** Summary changed:

- [ovn-octavia-provider] DVR traffic not reenabled for members' FIP upon cascade deletion
+ [ovn-octavia-provider] FIP traffic not distributed for members' FIP after lb cascade deletion

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

Title:
  [ovn-octavia-provider] FIP traffic not distributed for members' FIP
  after lb cascade deletion

Status in neutron:
  In Progress

Bug description:
  When a member of a loadbalancer has a FIP, it gets centralized (mac
  info removed from NAT table) due to requirements on OVN side. When a
  member gets deleted from a loadbalancer, the mac information gets
  updated in the NAT table and the traffic to the FIP gets distributed
  again. However, if the whole loadbalancer gets deleted with the
  cascade option, the traffic to the member FIP is left centralized
  (without the NAT table being updated with the MAC again)

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