agent instances are not rescheduled when one agent goes offline
Bug #1174591 reported by
Robert Collins
This bug affects 6 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Kevin Benton | ||
tripleo |
Invalid
|
Medium
|
Unassigned |
Bug Description
When an agent fails/goes offline for any reason, the services it was providing are unavailable until either the agent comes back or the work gets scheduled onto another agent - which is currently a manual task.
This is related to bug 1174132 which covers the impact of users when an agent fails and there is no agent running for a period of time.
Ideally, Quantum could ensure that rescheduling happens automatically, making the addition and removal of agents automatic - nearly free of configuration.
description: | updated |
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in quantum: | |
status: | New → Confirmed |
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
assignee: | nobody → Kevin Benton (kevinbenton) |
status: | Confirmed → In Progress |
Changed in neutron: | |
importance: | Undecided → Medium |
Changed in neutron: | |
assignee: | Kevin Benton (kevinbenton) → Eugene Nikanorov (enikanorov) |
Changed in neutron: | |
milestone: | none → liberty-2 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | liberty-2 → 7.0.0 |
To post a comment you must log in.
Automatic scheduling is something that is planned.