[ovn-octavia-provider] FIP traffic not distributed for members' FIP after lb cascade deletion
Bug #2025637 reported by
Luis Tomas
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Committed
|
Medium
|
Luis Tomas | ||
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)
| Changed in neutron: | |
| assignee: | nobody → Luis Tomas (luis5tb) |
| status: | New → In Progress |
| summary: |
- [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 |
| Changed in neutron: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Luis Tomas (luis5tb) wrote | #1 |
| Changed in neutron: | |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ovn-octavia-provider 2.2.0 | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ovn-octavia-provider 5.0.0.0rc1 | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ovn-octavia-provider 3.1.2 | #4 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ovn-octavia-provider wallaby-eom | #5 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/ovn-octavia-provider xena-eom | #6 |
To post a comment you must log in.
fix: https:/