| Thread Previous • Date Previous • Date Next • Thread Next |
Public bug reported:
This change broke the ability to force quotas below the current in-use
value by adding new validation checks:
https://review.openstack.org/#/c/28232/
$ nova quota-update --force --cores 0 132
ERROR (BadRequest): Quota limit must be greater than 1. (HTTP 400) (Request-ID: req-ff0751a9-9e87-443e-9965-a30768f91d9f)
** Affects: nova
Importance: Undecided
Assignee: Kieran Spear (kspear)
Status: New
** Changed in: nova
Assignee: (unassigned) => Kieran Spear (kspear)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1362405
Title:
'Force' option broken for quota update
Status in OpenStack Compute (Nova):
New
Bug description:
This change broke the ability to force quotas below the current in-use
value by adding new validation checks:
https://review.openstack.org/#/c/28232/
$ nova quota-update --force --cores 0 132
ERROR (BadRequest): Quota limit must be greater than 1. (HTTP 400) (Request-ID: req-ff0751a9-9e87-443e-9965-a30768f91d9f)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1362405/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |