Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1236605

Summary: The operation of create image has failed with not enough free quota storage although sufficient space was available
Product: Red Hat OpenStack Reporter: lkuchlan <lkuchlan>
Component: openstack-glanceAssignee: Flavio Percoco <fpercoco>
Status: CLOSED UPSTREAM QA Contact: nlevinki <nlevinki>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: eglynn, fpercoco, yeylon
Target Milestone: ---   
Target Release: 8.0 (Liberty)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 10:59:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
glance logs none

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.