No need to autoreschedule routers if l3 agent is back online
Bug #1522436 reported by
Oleg Bondarev
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Oleg Bondarev |
Bug Description
- in case l3 agent goes offline the auto-rescheduling task is triggered and starts to reschedule each router from dead agent one by one
- If there are a lot of routers scheduled to the agent, rescheduling all of them might take some time
- during that time the agent might get back online
- currently autorescheduling will be continued until all routers are rescheduled from the (already alive!) agent
The proposal is to skip rescheduling if agent is back online.
Changed in neutron: | |
importance: | Undecided → Medium |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
tags: | added: mitaka-backport-potential |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
tags: | removed: mitaka-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/252980
Review: https:/