Ask Your Question

Incorrect advertisement of block storage total and free space

asked 2015-04-27 08:15:20 -0600

Lluis Gifre gravatar image

Hi All,

I recently installed OpenStack IceHouse + OpenContrail v2.1 package. The package works, but the available total and free storage announced is not correct in the Admin > Hypervisors section of Horizon dashboard. It shows the total and free space in the root partition of the hypervisors instead of the cinder-volumes logical volume I created with LVM. However, cinder places the volumes in that cinder-volumes logical volume as expected.

Does somebody have an idea of which configuration parameter should I change to solve this problem?

Thanks, Lluis

edit retag flag offensive close merge delete


Hello Lluis. We have the same problem. We can use the LVM, but the space in the dashboard corresponds to the /root partition, insead of the LVM. Could you solved it?

gonza8888 gravatar imagegonza8888 ( 2015-08-26 11:38:52 -0600 )edit

Same here with default Liberty installation. This did prevent me from starting volumes as the local disk space was less than the logical volume managed by Cinder. I increased the disk_allocation_ratio to 10.0 in /etc/nova/nova.conf as a workaround, but would be interested in a proper fix.

chazapis gravatar imagechazapis ( 2015-11-17 07:44:44 -0600 )edit

Hello chazapis. Did this fix disk_allocation_ratio= 10.0 worked for you? I am facing similar situation and my ratio is 1.0 I am curious to know on this.

Sri Harsha Solasa gravatar imageSri Harsha Solasa ( 2016-05-23 15:55:55 -0600 )edit

4 answers

Sort by ยป oldest newest most voted

answered 2016-03-21 12:12:49 -0600

Lluis Gifre gravatar image

Hi all, I'm answering myself since I found a solution that worked to me.

I identified this same problem in Openstack Liberty and Juno and IMHO the installation guide for Liberty lacks a configuration of nova-compute service in the compute nodes. I already reported a bug.

I solved the problem by adding the next options in /etc/nova/nova.conf of each compute node:

[libvirt] images_type = lvm images_volume_group = cinder-volumes

Assume that LVM is used and the volume group is named as 'cinder-volumes'.

Then, you need to restart the nova-compute service in each compute node:

sudo service nova-compute restart

Now, the dashboard should report the correct storage size in your volume groups.

Hope it helps! Best, Lluis

edit flag offensive delete link more


Thank you Lluis seem it change to new value

golfreeze gravatar imagegolfreeze ( 2018-02-02 23:03:18 -0600 )edit

answered 2016-05-20 07:20:55 -0600

ZaphodB gravatar image

This seems to be a bug in nova compute which is currently being addressed. (

At the time of posting there was no release known which will integrate this patch yet. Will update when this is known.

edit flag offensive delete link more

answered 2016-10-07 19:26:07 -0600

Richard Hong gravatar image

I have the same issue, My openstack is liberty. And the nova report that have no valid host to build VM when the disk size of new vm is more bigger than the remaining disk size. but I build all vm in LVM block storage server, not compute node. And the options [libvirt] images_type = lvm images_volume_group = cinder-volumes are useless.

edit flag offensive delete link more


Hi Richard, can u pls explain how u create the volume in the LVM block storage server..?? I have only "nova" as availability zone hence can can create volumes in the compute nodes so no volume for the VM launch. Thanks for your support. Regards, mirony

mirony gravatar imagemirony ( 2017-04-21 07:43:05 -0600 )edit

answered 2018-02-02 23:02:03 -0600

Thanky you Lluis !

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2015-04-27 08:15:20 -0600

Seen: 2,931 times

Last updated: Oct 07 '16