L3 agent restart causes network outage
Bug #1175695 reported by
Jack McCann
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Stephen Ma | ||
Havana |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When L3 agent is restarted, it destroys all existing namespaces and then recreates them. This causes a network outage for the affected routers and floating IPs, even if those routers/floating IPs are still valid. We should be able to preserve existing, valid namespaces across an agent restart and avoid the network outage.
Changed in quantum: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in quantum: | |
assignee: | nobody → Jack McCann (jack-mccann) |
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
importance: | Medium → High |
tags: | added: havana-backport-potential |
Changed in neutron: | |
milestone: | none → icehouse-3 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/30988
Review: https:/