Create volume failures with log only showing "No valid host was found"

Bug #1136147 reported by John Griffith
6
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.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/23193

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/23193
Committed: http://github.com/openstack/cinder/commit/0c2ce65014be15430b37df83e12d970052a028b4
Submitter: Jenkins
Branch: master

commit 0c2ce65014be15430b37df83e12d970052a028b4
Author: John Griffith <email address hidden>
Date: Thu Feb 28 18:34:07 2013 +0000

    Add some useful log to filter scheduler.

    When the filter scheduler is unable to find a suitable host to
    deploy a volume on it simply logged a warning "not hosts found".
    This isn't very helpful, so this patch adds some logging info as
    far as why no valid host was available. This just focuses on the
    capacity filtering as that's where I've commonly seen this issue
    particularly in tempest runs.

    Also noticed that the get status was checking for "if Not capacity",
    but this is wrong because free capacity==0 would be interpretted as
    failing to get capacity. Change this to "if is None".

    Fixes bug: 1136147

    Change-Id: Ia1ce508826ee69ae68a250ea68616909c59974e5

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in cinder:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in cinder:
milestone: grizzly-rc1 → 2013.1
Revision history for this message
Shanthakumar K (shantha-kumar) wrote :

I using multinode cinder in my openstack setup, i could see the second node added with controller.

I am able to create the volume in controller node, where i have cinder installed but i couldnt create the volume on other node.

FYI - When i tried to create the volume from second also, its getting created in controller node only....

When am I scheduling to create the volume on cinder node im getting ''no valid host found"

cinder .conf on second node.

[DEFAULT]
rootwrap_config=/etc/cinder/rootwrap.conf
sql_connection = mysql://cinderUser:cinderPass@10.1.0.29/cinder
api_paste_confg = /etc/cinder/api-paste.ini
iscsi_helper=ietadm
volume_name_template = volume-%s
volume_group = cinder-volumes
rabbit_host = 10.1.0.29
volumes_dir = /etc/cinder/volumes
state_path = /var/lib/cinder
lock_path = /var/lock/cinder
verbose = True
auth_strategy = keystone
#debug=true
#osapi_volume_listen_port=5900

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.