yahoo-eng-team team mailing list archive

[Alex Meade <1258331@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Glance v2 image property quota enforcement can be unintuitive.

There are a number of reasons an image may have more properties than the
image_propery_quota allows. E.g. if the quota is lowered or when it is
first created. If this happens then any request to modify an image must
result in the image being under the new quota. This means that even if
the user is removing quotas they can still get an 413 overlimit from
glance if the result would still be over the limit.

This is not a great user experience and is unintuitive. Ideally a user
should be able to remove properties or any other action except for
adding a property when they are over their quota for a given image.

** Affects: glance
     Importance: Medium
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1258331

Title:
  Glance v2: Image property quotas are unforgiving when quota is
  exceeded

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  Glance v2 image property quota enforcement can be unintuitive.

  There are a number of reasons an image may have more properties than
  the image_propery_quota allows. E.g. if the quota is lowered or when
  it is first created. If this happens then any request to modify an
  image must result in the image being under the new quota. This means
  that even if the user is removing quotas they can still get an 413
  overlimit from glance if the result would still be over the limit.

  This is not a great user experience and is unintuitive. Ideally a user
  should be able to remove properties or any other action except for
  adding a property when they are over their quota for a given image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1258331/+subscriptions