cinder capabilities filter fails in naive set up
Bug #1131011 reported by
Mandell
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Fix Released
|
Undecided
|
Huang Zhiteng | ||
Bug Description
If you enable the capability filter with no other set up (because, for instance, you have only one volume host, it is possible to have a traceback from host_manager.py. The problem stems from not checking if capability exists before attempting to access capability[
| Changed in cinder: | |
| assignee: | nobody → Huang Zhiteng (zhiteng-huang) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to cinder (master) | #1 |
| Changed in cinder: | |
| status: | In Progress → Fix Committed |
| Changed in cinder: | |
| milestone: | none → grizzly-3 |
| status: | Fix Committed → Fix Released |
| Changed in cinder: | |
| milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit 8169eb668321014
Author: Mandell Degerness <email address hidden>
Date: Thu Feb 21 02:59:44 2013 +0000
Skip timestamp check if 'capabilities' is none
fix bug: #1131011
Change-Id: I6266560627d03d