Activity log for bug #1470889

Date Who What changed Old value New value Message
2015-07-02 14:47:29 Oleg Bondarev bug added bug
2015-07-02 14:49:26 Oleg Bondarev description Currently If 'dvr' l3 agent on a compute node goes down, routers are removed from it; then when agent is up again routers are not added back - so VMs on that compute node lose all routing. Scheduling/unscheduling of DVR routers to the l3 agent in 'dvr' mode running on a compute node is done according to dvr serviced ports created/deleted on that compute node. It doesn't make sense to reschedule router from l3 agent on compute node even if it's down - no other l3 agent can handle VMs running on that compute node. Currently If 'dvr' l3 agent on a compute node goes down, routers are removed from it; then when agent is up again routers are not added back - so VMs on that compute node lose all routing. Scheduling/unscheduling of DVR routers to the l3 agent in 'dvr' mode running on a compute node is done according to dvr serviced ports created/deleted on that compute node. It doesn't make sense to reschedule router from l3 agent on compute node even if it's down - no other l3 agent can handle VMs running on that compute node.
2015-07-02 15:00:30 OpenStack Infra neutron: status New In Progress
2015-07-02 15:39:32 Oleg Bondarev tags l3-dvr-backlog kilo-backport-potential l3-dvr-backlog
2015-07-02 16:11:03 Assaf Muller neutron: importance Undecided High
2015-08-18 01:20:39 OpenStack Infra neutron: status In Progress Fix Committed
2015-08-31 12:09:13 OpenStack Infra tags kilo-backport-potential l3-dvr-backlog in-feature-pecan kilo-backport-potential l3-dvr-backlog
2015-09-03 19:06:37 Thierry Carrez neutron: status Fix Committed Fix Released
2015-09-03 19:06:37 Thierry Carrez neutron: milestone liberty-3
2015-10-15 12:29:33 Thierry Carrez neutron: milestone liberty-3 7.0.0