[
https://issues.apache.org/jira/browse/JCLOUDS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070058#comment-14070058
]
Chris Custine commented on JCLOUDS-268:
---------------------------------------
The new hpcloud-blockstorage provider uses the Cinder APIs and properly throws
an exception like this:
org.jclouds.rest.InsufficientResourcesException: {"overLimit": {"message":
"VolumeSizeExceedsAvailableQuota: Requested volume or snapshot exceeds allowed
Gigabytes quota. Requested 3001G, quota is 3000G and 1G has been consumed.",
"code": 413, "retryAfter": 0}}
The Nova Volume API (in hpcloud-compute) for a similar test throws an HTTP 500
error, so I will try to fix this, but I recommend moving Volume related calls
to use the Cinder (hpcloud-blockstoage) provider anyway.
> Getting null volumeID when creating a volume and have exceeded their quota
> --------------------------------------------------------------------------
>
> Key: JCLOUDS-268
> URL: https://issues.apache.org/jira/browse/JCLOUDS-268
> Project: jclouds
> Issue Type: Bug
> Reporter: Ravikumar Venkatesan
>
> while creating volumes and exceeding quota, it's not throwing an exceeded
> quota error, rather it's just showing them the volume IDs are null and it's
> not creating them.
> Is this by design or can we have jclouds show the exceed quota error like the
> API does?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
