Handle version for PUT and POST in PlacementFixture
The SchedulerReportClient allows a "version" keyword argument to be
specified for its get/put/post methods and several functions pass a
version because they are sending data supported only in specific
microversions of the placement API.
The PlacementFixture has to mock the SchedulerReportClient
get/put/post/delete methods to swap in a Keystone session with
auth=None. The fake methods for PUT and POST are missing handling of
the "version" keyword argument, causing intermittent "400 Bad Request"
failures in the functional test jobs when unexpected parameters are
passed to placement microversion 1.0 instead of the intended
microversion.
Reviewed: https:/ /review. openstack. org/478683 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=1d74a7ab3da 2a04e133347bd59 cb1e37e1c8e322
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1d74a7ab3da2a04 e133347bd59cb1e 37e1c8e322
Author: melanie witt <email address hidden>
Date: Wed Jun 28 23:50:53 2017 +0000
Handle version for PUT and POST in PlacementFixture
The SchedulerReport Client allows a "version" keyword argument to be
specified for its get/put/post methods and several functions pass a
version because they are sending data supported only in specific
microversions of the placement API.
The PlacementFixture has to mock the SchedulerReport Client put/post/ delete methods to swap in a Keystone session with
get/
auth=None. The fake methods for PUT and POST are missing handling of
the "version" keyword argument, causing intermittent "400 Bad Request"
failures in the functional test jobs when unexpected parameters are
passed to placement microversion 1.0 instead of the intended
microversion.
Closes-Bug: #1701129
Change-Id: I681712ac37f732 c7803c68f6c7d1e ae9f2877d3d