There is no Glance quota check for instance snapshot
If the user creates a snapshot for Compute instances and there is not sufficient quota available (e.g. for object store), the snapshot will fail with a non obvious error for the end user. The error message should point to the missing quota.
When user uploads an image and the swift quota is full, glance just resets the connection without notifying about the actual problem
I found https:/
https:/
but the bp doesnt seem to be implemented. Any suggestions how to proceed?
Actual glance log inside the container contains this:
2018-06-18 08:09:57,023.023 43 ERROR glance.common.wsgi [req-12ddd27e-
Got error from Swift: Object PUT failed: https:/
Got error from Swift: Object PUT failed: https:/
Regards,
Rajiv
Question information
- Language:
- English Edit question
- Status:
- Answered
- For:
- Glance Edit question
- Assignee:
- No assignee Edit question
- Last query:
- 2019-07-03
- Last reply:
- 2019-07-11
This question was reopened
- 2019-07-02 by Rajiv Mucheli
Could you provide some more information?
(1) How are you making the call (API, glanceclient, openstackclient, horizon)?
(2) What exactly is the error message you are receiving?
Also, from the log extract you posted, glance quotas won't help this problem ... the quota is being exceeded on the swift side when glance tries to store the image. (But I agree that you should be receiving a more helpful error message.)
Short term, if you are using the swift store in its default configuration, there's a glance user who owns *all* the images. Thus this user needs to have a high storage quota in swift. You should increase this user's quota.
Rajiv Mucheli (rajiv.mucheli) said : | #2 |
1) openstack client
2) When user uploads an image and the swift quota is full, glance just resets the connection without notifying about the actual problem:
$ openstack image create bio-windows-
Error finding address for https:/
Could you share more details on which user it is?
Rajiv Mucheli (rajiv.mucheli) said : | #3 |
changing status to need answer
Hi Rajiv,
Before you fix anything, can you see what happens when you use the glanceclient to create the image? Use 'glance image-create' instead of 'openstack image create'. I think all the options can be the same, except you'll need to add '--name' before the image name. (I'm curious whether the glanceclient handles this better.)
To determine the glance swift user, look in your glance-api.conf and see if 'swift_
Otherwise, check to see if there's a value for 'swift_
If there *is* a swift store config file, look in it for the value of the 'user' (format will be the same as above).
Rajiv Mucheli (rajiv.mucheli) said : | #5 |
Hi Bran,
The value is set to True : https:/
Value of swift_store_
Rajiv Mucheli (rajiv.mucheli) said : | #6 |
Hi Brian,
Could you please share an update ?
Regards,
Rajiv
Hi Rajiv,
The helm templates you point to will generate a glance configuration, but I can't tell from the templates what your configuration is. You need to look at the config that's generated (or your helm Values) to see whether you are using swift in multi-tenant or single-tenant mode.
If .Values.
Otherwise, you need to check .Values.
Can you help with this problem?
Provide an answer of your own, or ask Rajiv Mucheli for more information if necessary.