yahoo-eng-team team mailing list archive

[Chris Friesen <chris.friesen@xxxxxxxxxxxxx>]

Public bug reported:

It is supposed to be possible to specify the "force" option when
updating a quota-set.  Up to microversion 2.35 this works as expected.

However, in 2.36 it no longer works, and nova-api sends back:

RESP BODY: {"badRequest": {"message": "Invalid input for field/attribute
quota_set. Value: {u'cores': 95, u'force': True}. Additional properties
are not allowed (u'force' was unexpected)", "code": 400}}


The problem seems to be that in schemas/quota_sets.py the "force" parameter is not in quota_resources, but rather is added to "update_quota_set".  When creating update_quota_set_v236 they copied quota_resources instead of copying update_quota_set, and this meant that they lost the support for the "force" parameter.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: api ocata-backport-potential pike-backport-potential quotas

** Tags added: ocata-backport-potential pike-backport-potential quotas

-- 
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/1734394

Title:
  nova microversion 2.36 accidentally removed support for "force" when
  setting quotas

Status in OpenStack Compute (nova):
  New

Bug description:
  It is supposed to be possible to specify the "force" option when
  updating a quota-set.  Up to microversion 2.35 this works as expected.

  However, in 2.36 it no longer works, and nova-api sends back:

  RESP BODY: {"badRequest": {"message": "Invalid input for
  field/attribute quota_set. Value: {u'cores': 95, u'force': True}.
  Additional properties are not allowed (u'force' was unexpected)",
  "code": 400}}

  
  The problem seems to be that in schemas/quota_sets.py the "force" parameter is not in quota_resources, but rather is added to "update_quota_set".  When creating update_quota_set_v236 they copied quota_resources instead of copying update_quota_set, and this meant that they lost the support for the "force" parameter.

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