Multiple node compute doesn't support retry semantics
Bug #1081370 reported by
Brian Elliott
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Arata Notsu |
Bug Description
Commit 885cf0949ab2e11
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: baremetal |
Changed in nova: | |
assignee: | nobody → Arata Notsu (arata776) |
status: | Triaged → In Progress |
Changed in nova: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/16799 github. com/openstack/ nova/commit/ f87c2e8334306cb 7ef78b64a4bf594 9b73d87617
Committed: http://
Submitter: Jenkins
Branch: master
commit f87c2e8334306cb 7ef78b64a4bf594 9b73d87617
Author: Arata Notsu <email address hidden>
Date: Sat Nov 24 02:09:25 2012 +0900
RetryFilter checks 'node' as well as 'host'
FilterScheduler and RetryFilter use "(host, node)" instead of "host" to
filter candidates. It makes rescheduling on different nodes in the same
host possible.
Fix bug 1081370
Change-Id: Id51b262de7b47b 5f9215463eca5ae 07a29109c3f