BGP: DVR fip host routes query including legacy/HA fip routes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
LIU Yulong |
Bug Description
ENV:
neutron-8.1.2-1 (stable/mitaka)
When query a bgpspeaker's routes, the DVR fip host routes query will get the routes including the central fip routes.
This will let the central fip has more than one next_hop routes.
For instance:
+------
| destination | next_hop |
+------
| 172.16.10.69/32 | 172.16.10.57 | (ha)
| 172.16.10.69/32 | 172.16.10.65 | (ha)
| 172.16.10.70/32 | 172.16.10.58 | (legacy)
| 172.16.10.70/32 | 172.16.10.66 | (legacy)
| 172.16.10.68/32 | 172.16.10.66 | (dvr)
| 172.16.10.67/32 | 172.16.10.65 | (ha-and-dvr)
+------
public (external) network ports:
172.16.10.69 network:floatingip
172.16.10.70 network:floatingip
172.16.10.68 network:floatingip
172.16.10.67 network:floatingip
172.16.10.66 network:
172.16.10.65 network:
172.16.10.59 network:
172.16.10.57 network:
172.16.10.58 network:
172.16.10.60 network:
This issue was tested in stable/mitaka, bug the upstream may also have the same issue.
Because this line did not filter the legacy/HA fips' routes:
https:/
bgp routes, Routers, floating IPs, ports, networks:
http://
tags: | added: l3-bgp |
summary: |
- BGP: DVR fip host routes query including legacy/HA fip routs + BGP: DVR fip host routes query including legacy/HA fip routes |
description: | updated |
description: | updated |
tags: | added: mitaka-backport-potential |
tags: | removed: mitaka-backport-potential |
Fix proposed to branch: master /review. openstack. org/349401
Review: https:/