yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #69385
[Bug 1733886] [NEW] 'force' parameter broken in os-quota-sets microversion >= 2.36
Public bug reported:
The 2.36 microversion broke the 'force' parameter in the os-quota-sets
API:
https://developer.openstack.org/api-ref/compute/#update-quotas
It's because for 2.36 the schema redefined the properties but didn't
copy the force parameter:
https://github.com/openstack/nova/blob/f69d98ea744bc13189b17ba4c67e4f0279d2f45a/nova/api/openstack/compute/schemas/quota_sets.py#L47
We could fix this as part of blueprint deprecate-file-injection which
needs to change the os-quota-sets API to remove the injected_file*
parameters, however, after the counting quotas changes in Pike, the
'force' parameter doesn't really mean anything because there are no
reserved quotas anymore, so maybe we just document this in the API
reference and not try to 'fix it' since the fix wouldn't do anything.
** Affects: nova
Importance: Undecided
Status: New
--
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/1733886
Title:
'force' parameter broken in os-quota-sets microversion >= 2.36
Status in OpenStack Compute (nova):
New
Bug description:
The 2.36 microversion broke the 'force' parameter in the os-quota-sets
API:
https://developer.openstack.org/api-ref/compute/#update-quotas
It's because for 2.36 the schema redefined the properties but didn't
copy the force parameter:
https://github.com/openstack/nova/blob/f69d98ea744bc13189b17ba4c67e4f0279d2f45a/nova/api/openstack/compute/schemas/quota_sets.py#L47
We could fix this as part of blueprint deprecate-file-injection which
needs to change the os-quota-sets API to remove the injected_file*
parameters, however, after the counting quotas changes in Pike, the
'force' parameter doesn't really mean anything because there are no
reserved quotas anymore, so maybe we just document this in the API
reference and not try to 'fix it' since the fix wouldn't do anything.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1733886/+subscriptions
Follow ups