The placement consumer generation conflict error message can be misleading

[Chris Dent]

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.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/577171

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/577171
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=07460610f8de0c6d224a0a3dea8d9ead63c61bcc
Submitter: Zuul
Branch: master

commit 07460610f8de0c6d224a0a3dea8d9ead63c61bcc
Author: Eric Fried <email address hidden>
Date: Thu Jun 21 09:16:17 2018 -0500

    placement: s/None/null/ in consumer conflict msg

    The placement API had a message complaining that it was "expecting None"
    which is python-speak when it should be JSON speak. This change
    corrects the message and adds a gabbi test for it.

    Change-Id: Ibfb3d581588c8eb954a9faca19d9cb26d2c28861
    Closes-Bug: #1778071

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/nova 18.0.0.0b3 development milestone.