Create volume failures with log only showing "No valid host was found"
Bug #1136147 reported by
John Griffith
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
John Griffith |
Bug Description
A number of things can cause a volume create to fail when going through the filter scheduler, the most common of course is capacity issues. Unfortunately right now the logging isn't very helpful. We should add some logging to the scheduler code to give more information on why a host could not be found, and also the failed to find hosts log messages should be elevated to error, not just warnings.
Changed in cinder: | |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | grizzly-rc1 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/23193
Review: https:/