Ask Your Question
1

Is there any way to find out why a volume creation failed without having to open the log files?

asked 2014-06-02 10:21:11 -0600

ecerulm gravatar image

updated 2014-06-03 01:10:22 -0600

As an example, I was trying to create a 20GB volume in my OpenStack test installation and it fails. It fails because the quota for the tenant that I'm using only allows volumes up to 10GB which is ok, it should fail.

But cinder show xxx only says that the status is error, it doesn't tell me why it failed. I had to go and read the /var/log/syslog to find out that the problem was with the quotas (I think I say a mention to cinder-scheduler and capacity.filter saying that only 10GB were available and from there I found the quota thing)

It's there any way to find out the details of why a cinder volume creation failed, without having to access the /var/log/* which may not be accesible if I'm creating the volume remotely.

edit retag flag offensive close merge delete

Comments

View logs under /var/log/cinder. And volume.log in particular. On compute node view /var/log/nova/nova-compute.log , if you create volume via image at booting up.

dbaxps gravatar imagedbaxps ( 2014-06-02 11:54:15 -0600 )edit

3 answers

Sort by ยป oldest newest most voted
1

answered 2014-06-03 01:36:01 -0600

manish gravatar image

No need to look into logs for quota related error . It will give error message on console or GUI if you are trying to create volume more then quota. here is the message which i have got on console and GUI it self. "ERROR: VolumeSizeExceedsAvailableQuota: Requested volume or snapshot exceeds allowed Gigabytes quota. Requested 11G, quota is 10G and 5G has been consumed."

edit flag offensive delete link more

Comments

I don't see that error in the console at all (I'm using "DevStack Havana) and the "error" I see in the /var/log has a complete different wording. Also for me the cinder create xxx returns immediately, I have to cinder list a couple of times until I see the error.

ecerulm gravatar imageecerulm ( 2014-06-03 04:34:34 -0600 )edit
1

answered 2014-06-02 11:56:17 -0600

dbaxps gravatar image

updated 2014-06-02 11:57:14 -0600

View logs under /var/log/cinder. And volume.log in particular. On compute node view /var/log/nova/nova-compute.log , if you create volume via image at booting up.
edit flag offensive delete link more

Comments

By syslog I meant the whole /var/log

ecerulm gravatar imageecerulm ( 2014-06-03 01:09:31 -0600 )edit
0

answered 2014-11-01 20:54:05 -0600

LZ gravatar image

DevStack default create volume groups of 10GB.

use vgs command will show you the size

> vgs
VG              #PV #LV #SN Attr    VSize   VFree
stack-volumes   1   2   0   wz--n-  10.00g  10.00g

You can change that in local.conf before run ./stack.sh

Add following to your local.conf

VOLUME_BACKING_FILE_SIZE=  <size here>

Then run ./stack.sh now u will have whatever you set for volume max size.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-06-02 10:21:11 -0600

Seen: 2,502 times

Last updated: Nov 01 '14