yahoo-eng-team team mailing list archive

[Benjamin Beier <2128215@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hello everyone,

we are using the new unified limits API and noticed some impractical (possibly bugged?) behavior in regards to registered default limits and project limits.
To set a default limit for the whole region we use the "registered limit create" command.
Of course certain projects will require more resources than the default allows for and we set project limits using the "limit create" command.
Now the problem arises when at any point in time you decide that you want to increase the default limit.
In this case we use the "registered limit set" command, which will respond wit the following error:

"Unable to update or delete registered limit
e5cbea0ee0ce4e458b4c602b8e6258de because there are project limits
associated with it. (HTTP 403)"

Of course it does make sense that you can't delete a registered limit when there are project limits associated with it, but why does it also prevent updates on the registered limit?
Right now you can either mess around in the database to increase a registered limit or you are forced to delete all project limits, change the registered limit and then recreate all project limits again, which is obviously very impractical.

Is this actually the intended behavior or a bug and where does this
restriction on registered limit updates come from?

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/2128215

Title:
  Registered limits can't be updated

Status in OpenStack Identity (keystone):
  New

Bug description:
  Hello everyone,

  we are using the new unified limits API and noticed some impractical (possibly bugged?) behavior in regards to registered default limits and project limits.
  To set a default limit for the whole region we use the "registered limit create" command.
  Of course certain projects will require more resources than the default allows for and we set project limits using the "limit create" command.
  Now the problem arises when at any point in time you decide that you want to increase the default limit.
  In this case we use the "registered limit set" command, which will respond wit the following error:

  "Unable to update or delete registered limit
  e5cbea0ee0ce4e458b4c602b8e6258de because there are project limits
  associated with it. (HTTP 403)"

  Of course it does make sense that you can't delete a registered limit when there are project limits associated with it, but why does it also prevent updates on the registered limit?
  Right now you can either mess around in the database to increase a registered limit or you are forced to delete all project limits, change the registered limit and then recreate all project limits again, which is obviously very impractical.

  Is this actually the intended behavior or a bug and where does this
  restriction on registered limit updates come from?

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