yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

When using consumer generations to create new allocations, the value of
the generation is expected to be None on the python side, and 'null' in
JSON. The error response sent over the API says "expected None but got
1" which doesn't help much since the api is in JSON.

** Affects: nova
     Importance: Low
     Assignee: Eric Fried (efried)
         Status: In Progress


** Tags: placement

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

Title:
  The placement consumer generation conflict error message can be
  misleading

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  When using consumer generations to create new allocations, the value
  of the generation is expected to be None on the python side, and
  'null' in JSON. The error response sent over the API says "expected
  None but got 1" which doesn't help much since the api is in JSON.

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