Hi Eduard,
According to the error you had, I assume your volume format is sparse
(probably qcow2). When you create a volume out of it, Cinder will convert
the format to 'raw', which increases its size. I believe the 'size'
parameter is now optional if you create a volume from a source (such as
image, snapshot, or other volume).
With regard to your question on how to view this on the client side, if the
volume goes to 'error' state, there is no way to know why right now without
checking logs. Yes, this is bad.
Thanks,
Avishay
On Fri, Oct 3, 2014 at 10:06 AM, Eduard Matei
eduard.ma...@cloudfounders.com wrote:
Hi,
I'm creating a cinder volume from a glance image (Fedora).
The image is 199 Mb and since it's for testing, i created a volume of size
1GB.
This fails, and puts image in status Error. (without any more info)
Digging through screens i found an exception ImageUnacceptable (size is 2
GB and doesn't fit ...).
Is there a way to get this exception on the client side?
e.g. cinder show VOLUMEID to contain the exception message
Thanks,
--
*Eduard Biceri Matei, Senior Software Developer*
www.cloudfounders.com
| eduard.ma...@cloudfounders.com
*CloudFounders, The Private Cloud Software Company*
Disclaimer:
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you are not the named addressee or an employee or agent responsible for
delivering this message to the named addressee, you are hereby notified that
you are not authorized to read, print, retain, copy or disseminate this
message or any part of it. If you have received this email in error we
request you to notify us by reply e-mail and to delete all electronic files
of the message. If you are not the intended recipient you are notified that
disclosing, copying, distributing or taking any action in reliance on the
contents of this information is strictly prohibited.
E-mail transmission cannot be guaranteed to be secure or error free as
information could be intercepted, corrupted, lost, destroyed, arrive late or
incomplete, or contain viruses. The sender therefore does not accept
liability for any errors or omissions in the content of this message, and
shall have no liability for any loss or damage suffered by the user, which
arise as a result of e-mail transmission.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
