Time of "no capabilities" after nova-compute starts
Bug #1068114 reported by
Arata Notsu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Arata Notsu | ||
Bug Description
After a nova-compute starts, it takes some time for the capabilities to be sent to schedulers. It may make the schedulers send unacceptable requests to the nova-compute. It is most likely when the nova-compute runs for the first time; an entry in compute_nodes table is created, but the schedulers still don't know its capabilities, then the schedulers assume that the nova-compute has empty capabilities.
| Changed in nova: | |
| assignee: | nobody → Arata Notsu (arata776) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #1 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → grizzly-1 |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit e21d8ec390f3e02
Author: Arata Notsu <email address hidden>
Date: Thu Oct 18 20:00:44 2012 +0900
nova-compute sends its capabilities to schedulers ASAP
Fixes Bug 1068114.
When a nova-compute runs for the first time, after an entry in
compute_nodes table is created, it takes some time for the
capabilities to be sent to schedulers. It may make the schedulers
send unacceptable requests to the nova-compute. This patch eliminates
it by sending the capabilities before creating the entry in compute_node.
Change-Id: Id9851d9a6f0305