| 2016-08-01 08:05:33 |
LIU Yulong |
bug |
|
|
added bug |
| 2016-08-01 08:06:01 |
LIU Yulong |
tags |
|
l3-bgp |
|
| 2016-08-01 08:23:27 |
OpenStack Infra |
neutron: status |
New |
In Progress |
|
| 2016-08-01 08:23:27 |
OpenStack Infra |
neutron: assignee |
|
LIU Yulong (dragon889) |
|
| 2016-08-01 08:24:05 |
LIU Yulong |
summary |
BGP: DVR fip host routes query including legacy/HA fip routs |
BGP: DVR fip host routes query including legacy/HA fip routes |
|
| 2016-08-03 01:47:35 |
LIU Yulong |
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:floatingip_agent_gateway
172.16.10.65 network:floatingip_agent_gateway
172.16.10.59 network:router_gateway
172.16.10.57 network:router_gateway
172.16.10.58 network:router_gateway
172.16.10.60 network:router_gateway
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://github.com/openstack/neutron-dynamic-routing/blob/master/neutron_dynamic_routing/db/bgp_db.py#L732 |
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:floatingip_agent_gateway
172.16.10.65 network:floatingip_agent_gateway
172.16.10.59 network:router_gateway
172.16.10.57 network:router_gateway
172.16.10.58 network:router_gateway
172.16.10.60 network:router_gateway
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://github.com/openstack/neutron-dynamic-routing/blob/master/neutron_dynamic_routing/db/bgp_db.py#L732
bgp routes, Routers, floating IPs, ports, networks:
http://paste.openstack.org/show/547687/ |
|
| 2016-08-03 01:51:13 |
LIU Yulong |
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:floatingip_agent_gateway
172.16.10.65 network:floatingip_agent_gateway
172.16.10.59 network:router_gateway
172.16.10.57 network:router_gateway
172.16.10.58 network:router_gateway
172.16.10.60 network:router_gateway
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://github.com/openstack/neutron-dynamic-routing/blob/master/neutron_dynamic_routing/db/bgp_db.py#L732
bgp routes, Routers, floating IPs, ports, networks:
http://paste.openstack.org/show/547687/ |
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:floatingip_agent_gateway
172.16.10.65 network:floatingip_agent_gateway
172.16.10.59 network:router_gateway
172.16.10.57 network:router_gateway
172.16.10.58 network:router_gateway
172.16.10.60 network:router_gateway
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://github.com/openstack/neutron-dynamic-routing/blob/master/neutron_dynamic_routing/db/bgp_db.py#L732
bgp routes, Routers, floating IPs, ports, networks:
http://paste.openstack.org/show/547689/ |
|
| 2016-08-04 15:42:45 |
Brian Haley |
tags |
l3-bgp |
l3-bgp mitaka-backport-potential |
|
| 2016-08-08 18:40:06 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2016-08-09 23:14:17 |
OpenStack Infra |
tags |
l3-bgp mitaka-backport-potential |
in-stable-mitaka l3-bgp mitaka-backport-potential |
|
| 2016-10-07 16:21:30 |
Ihar Hrachyshka |
tags |
in-stable-mitaka l3-bgp mitaka-backport-potential |
in-stable-mitaka l3-bgp |
|
