[Openstack-operators] nova-volume discrepencies
alopgeek at gmail.com
Wed Jan 30 20:35:26 UTC 2013
I'm seeing some discrepancies in my essex nova-volume deploy.
According to the dashboard, I have about 17TB worth of volumes.
According to my backend storage system, I have about 80TB available
When I try to create a 500GB volumes, scheduler throws an error:
2013-01-30 19:05:00 WARNING nova.scheduler.manager [req-1f0db7ca-3453-4140-89a3-798b8d6c011e e57fef37fd9d47d79f5c3e3123119dbb 3675684cdf05472f9586752fc7e6fb51] Failed to schedule_create_volume: No valid host was found. Not enough allocatable volume gigabytes remaining
2013-01-30 19:05:00 TRACE nova.rpc.amqp File "/usr/lib/python2.7/dist-packages/nova/scheduler/simple.py", line 138, in schedule_create_volume
2013-01-30 19:05:00 TRACE nova.rpc.amqp NoValidHost: No valid host was found. Not enough allocatable volume gigabytes remaining
I've set the quota ridiculously high for this tenant, yet nothing seems to work.
I can create 100GB, 200GB, but after about 500GB, it throws the error.
Anyone know how the scheduler is making this determination?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the OpenStack-operators