Only one instance of a DHCP agent is run per network
Bug #1174132 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Gary Kotton | ||
tripleo |
Fix Released
|
Medium
|
Ryan O'Hara |
Bug Description
DHCP Agent's are stateless and can run HA, but the scheduler only schedules one instance - when a network node fails (or is rebooted / has maintenance done on it) this results in user visible downtime.
See also bug 1174591 which talks about the administrative overhead of dealing with failed nodes.
Changed in quantum: | |
status: | Opinion → Confirmed |
description: | updated |
Changed in quantum: | |
milestone: | none → havana-1 |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
tags: | added: grizzly-backport-potential |
Changed in tripleo: | |
importance: | High → Medium |
Changed in neutron: | |
milestone: | havana-1 → 2013.2 |
Changed in tripleo: | |
assignee: | nobody → Ryan O'Hara (rohara) |
tags: | removed: grizzly-backport-potential |
Changed in tripleo: | |
status: | In Progress → Fix Committed |
Changed in tripleo: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/ /etherpad. openstack. org/HavanaBareM etalVLAN was the summit discussion about this.