| 2016-06-29 18:06:44 |
Ann Taraday |
bug |
|
|
added bug |
| 2016-06-29 18:06:44 |
Ann Taraday |
attachment added |
|
openvswitch agent logs https://bugs.launchpad.net/bugs/1597461/+attachment/4692415/+files/neutron-openvswitch-agent.log.3.gz |
|
| 2016-06-29 18:09:10 |
Ann Taraday |
attachment added |
|
l3-agent logs https://bugs.launchpad.net/neutron/+bug/1597461/+attachment/4692416/+files/neutron-l3-agent.log.3.gz |
|
| 2016-07-04 09:03:38 |
Ann Taraday |
summary |
L3 HA + DVR: 2 masters after reboot of controller |
L3 HA: 2 masters after reboot of controller |
|
| 2016-07-04 09:06:42 |
Ann Taraday |
description |
ENV: Mitaka 3 controllers 45 computes DVR + L3 HA
After reboot of controller on which l3 agent is active, another l3 agent becomes active. When rebooted node recover, that l3 agent becomes active as well - this lead to extra loss of external connectivity in tenant network. After some time the only one agent remains to be active - the one from rebooted node. Sometimes connectivity does not come back, as snat port ends up on wrong host.
The root cause of this problem is that routers are processed by l3 agent before openvswitch agent sets up appropriate ha ports, so for some time recovered ha routers is isolated from ha routers on other hosts and becomes active.
The possible solution for this is proper serialization of ha network creation by l3 agent after ha network is set up on controller.
With 100 routers and networks this issues has been reproduced with every reboot. |
ENV: Mitaka 3 controllers 45 computes DVR + L3 HA
After reboot of controller on which l3 agent is active, another l3 agent becomes active. When rebooted node recover, that l3 agent becomes active as well - this lead to extra loss of external connectivity in tenant network. After some time the only one agent remains to be active - the one from rebooted node. Sometimes connectivity does not come back, as snat port ends up on wrong host.
The root cause of this problem is that routers are processed by l3 agent before openvswitch agent sets up appropriate ha ports, so for some time recovered ha routers is isolated from ha routers on other hosts and becomes active.
The possible solution for this is proper serialization of ha network creation by l3 agent after ha network is set up on controller.
With 100 routers and networks this issues has been reproduced with every reboot.
Actually this is L3 HA problem, it is just increased with DVR as the number of ports that openvswith agent should handle is higher. |
|
| 2016-07-04 09:15:47 |
Ann Taraday |
neutron: assignee |
|
Ann Taraday (akamyshnikova) |
|
| 2016-07-04 09:35:33 |
Ann Taraday |
description |
ENV: Mitaka 3 controllers 45 computes DVR + L3 HA
After reboot of controller on which l3 agent is active, another l3 agent becomes active. When rebooted node recover, that l3 agent becomes active as well - this lead to extra loss of external connectivity in tenant network. After some time the only one agent remains to be active - the one from rebooted node. Sometimes connectivity does not come back, as snat port ends up on wrong host.
The root cause of this problem is that routers are processed by l3 agent before openvswitch agent sets up appropriate ha ports, so for some time recovered ha routers is isolated from ha routers on other hosts and becomes active.
The possible solution for this is proper serialization of ha network creation by l3 agent after ha network is set up on controller.
With 100 routers and networks this issues has been reproduced with every reboot.
Actually this is L3 HA problem, it is just increased with DVR as the number of ports that openvswith agent should handle is higher. |
ENV: Mitaka 3 controllers 45 computes DVR + L3 HA (L3 HA as well affected)
After reboot of controller on which l3 agent is active, another l3 agent becomes active. When rebooted node recover, that l3 agent becomes active as well - this lead to extra loss of external connectivity in tenant network. After some time the only one agent remains to be active - the one from rebooted node. Sometimes connectivity does not come back, as snat port ends up on wrong host.
The root cause of this problem is that routers are processed by l3 agent before openvswitch agent sets up appropriate ha ports, so for some time recovered ha routers is isolated from ha routers on other hosts and becomes active.
The possible solution for this is proper serialization of ha network creation by l3 agent after ha network is set up on controller.
With 100 routers and networks this issues has been reproduced with every reboot.
Actually this is L3 HA problem, it is just increased with DVR as the number of ports that openvswith agent should handle is higher. |
|
| 2016-07-04 10:53:36 |
Rossella Sblendido |
neutron: status |
New |
Confirmed |
|
| 2016-07-07 12:06:35 |
John Schwarz |
bug |
|
|
added subscriber John Schwarz |
| 2016-07-11 16:35:46 |
Brian Haley |
bug |
|
|
added subscriber Brian Haley |
| 2016-07-22 11:07:37 |
Ann Taraday |
neutron: importance |
Undecided |
High |
|
| 2016-07-26 16:15:48 |
Gustavo Randich |
bug |
|
|
added subscriber Gustavo Randich |
| 2016-08-16 23:05:10 |
Hemachandra Reddy |
bug |
|
|
added subscriber Hemachandra Reddy |
| 2016-08-18 20:29:52 |
OpenStack Infra |
neutron: status |
Confirmed |
In Progress |
|
| 2016-08-23 13:40:48 |
OpenStack Infra |
neutron: assignee |
Ann Taraday (akamyshnikova) |
venkata anil (anil-venkata) |
|
| 2016-08-23 14:10:12 |
Ann Taraday |
neutron: assignee |
venkata anil (anil-venkata) |
Ann Taraday (akamyshnikova) |
|
| 2016-08-24 08:34:00 |
OpenStack Infra |
neutron: assignee |
Ann Taraday (akamyshnikova) |
venkata anil (anil-venkata) |
|
| 2016-08-26 13:30:19 |
OpenStack Infra |
neutron: assignee |
venkata anil (anil-venkata) |
Ann Taraday (akamyshnikova) |
|
| 2016-08-26 23:24:56 |
Randeep Jalli |
bug |
|
|
added subscriber Randeep Jalli |
| 2016-08-29 15:54:20 |
Kayla Fromme |
bug |
|
|
added subscriber Kayla Fromme |
| 2016-08-29 16:31:54 |
OpenStack Infra |
neutron: assignee |
Ann Taraday (akamyshnikova) |
John Schwarz (jschwarz) |
|
| 2016-08-29 20:56:21 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2016-09-02 12:37:15 |
Gustavo Randich |
bug watch added |
|
https://github.com/acassen/keepalived/issues/107 |
|
| 2016-09-11 19:33:41 |
Aaron C |
bug |
|
|
added subscriber Aaron C |
| 2016-10-13 17:12:06 |
OpenStack Infra |
tags |
l3-dvr-backlog l3-ha |
in-stable-mitaka l3-dvr-backlog l3-ha |
|
| 2017-01-04 00:59:46 |
Adam Spiers |
bug |
|
|
added subscriber Adam Spiers |
| 2017-05-26 08:49:35 |
Miguel Angel Ajo |
neutron: status |
Fix Released |
Confirmed |
|
| 2017-05-26 14:51:34 |
venkata anil |
neutron: assignee |
John Schwarz (jschwarz) |
venkata anil (anil-venkata) |
|
| 2017-06-05 09:57:40 |
OpenStack Infra |
neutron: status |
Confirmed |
In Progress |
|
| 2017-06-13 12:47:25 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2017-06-13 20:02:52 |
OpenStack Infra |
tags |
in-stable-mitaka l3-dvr-backlog l3-ha |
in-stable-mitaka in-stable-ocata l3-dvr-backlog l3-ha |
|
| 2017-06-14 16:59:25 |
OpenStack Infra |
tags |
in-stable-mitaka in-stable-ocata l3-dvr-backlog l3-ha |
in-stable-mitaka in-stable-newton in-stable-ocata l3-dvr-backlog l3-ha |
|
| 2017-12-01 23:36:08 |
OpenStack Infra |
tags |
in-stable-mitaka in-stable-newton in-stable-ocata l3-dvr-backlog l3-ha |
in-stable-mitaka in-stable-newton in-stable-ocata in-stable-pike l3-dvr-backlog l3-ha |
|
| 2018-04-16 10:39:29 |
Dominique Poulain |
bug |
|
|
added subscriber Dominique Poulain |
