Bug 1236605 - The operation of create image has failed with not enough free quota storage although sufficient space was available
Summary: The operation of create image has failed with not enough free quota storage a...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-glance
Version: 7.0 (Kilo)
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: 8.0 (Liberty)
Assignee: Flavio Percoco
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-29 14:19 UTC by lkuchlan
Modified: 2016-04-26 15:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 10:59:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
glance logs (419.67 KB, application/x-gzip)
2015-06-29 14:19 UTC, lkuchlan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1469738 0 None None None Never

Description lkuchlan 2015-06-29 14:19:34 UTC
Created attachment 1044378 [details]
glance logs

Description of problem:
Creating an image has failed with error message:"Denying attempt to upload image because it exceeds the quota", although there was enough space for upload the image

Version-Release number of selected component (if applicable):
python-glanceclient-0.17.0-2.el7ost.noarch
python-glance-2015.1.0-6.el7ost.noarch
python-glance-store-0.4.0-1.el7ost.noarch
openstack-glance-2015.1.0-6.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
With only cirros image(size=12.6MB) run those steps
1. Edit /etc/glance/glance-api.conf set user_storage_quota =1536000
2. openstack-service restart glance
3. Try to upload an image less than 1536000MB

Actual results:
Failed with 'Denying attempt to upload image because it exceeds the quota'

Expected results:
Creating an image should succeed 

Additional info:
It is similar to bug id=1043929
Glance logs

Comment 3 Flavio Percoco 2015-06-30 10:59:34 UTC
If the units are not specified, the value will be read as Bytes, which is why this error is being raised. You could try setting a different unit at the end of the value. For example,  1536000MB

I'm closing this as an upstream bug.


Note You need to log in before you can comment on or make changes to this bug.