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 protected]> 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 ** Changed in: nova Status: In Progress => Fix Released -- 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): Fix Released 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
