Compute 'force_service_down' API returns 400 with current version 2.72

Bug #1821584 reported by Shilpa Devharakar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-openstacksdk (Ubuntu)
In Progress
Undecided
Shilpa Devharakar

Bug Description

Bug Description:
-----------------
Openstacksdk returns 200 response for compute 'force_service_down' API with version 2.52
But with version 2.53 onwards, it returns 400

Observed that compute version 2.53 onwards 'force_service_down' API is superseded at
https://github.com/openstack/nova/commit/2f7bf29d472d349759ffd8aece23a75f4e27a4f9#diff-f04ac2da81ec6e182a88634657e150c7R204

And relevant changes which are needed at openstacksdk are not there.

Error log:
----------
DEBUG nova.api.openstack.wsgi [None req-98ed7264-002c-488b-94b4-47b00bf9b4f3 admin admin] Action: 'update', calling method: <function version_select at 0x7fc1603baed8>, body: {"binary": "nova-compute", "host": "<HOST_NAME>", "forced_down": true} {{(pid=1062) _process_stack /opt/stack/nova/nova/api/openstack/wsgi.py:520}}
DEBUG nova.api.openstack.wsgi [None req-98ed7264-002c-488b-94b4-47b00bf9b4f3 admin admin] Returning 400 to user: Additional properties are not allowed (u'binary', u'host' were unexpected) {{(pid=1062) __call__ /opt/stack/nova/nova/api/openstack/wsgi.py:943}}
INFO nova.api.openstack.requestlog [None req-98ed7264-002c-488b-94b4-47b00bf9b4f3 admin admin] 10.232.48.201 "PUT /compute/v2.1/os-services/force-down" status: 400 len: 118 microversion: 2.72 time: 0.004179
[pid: 1062|app: 0|req: 260/517] 10.232.48.201 () {68 vars in 1415 bytes} [Mon Mar 25 12:16:58 2019] PUT /compute/v2.1/os-services/force-down => generated 118 bytes in 5 msecs (HTTP/1.1 400) 9 headers in 383 bytes (1 switches on core 0)

Expected:
---------
Openstacksdk should return 200 response for compute 'force_service_down' API with current version i.e.2.72

Changed in python-openstacksdk (Ubuntu):
assignee: nobody → Shilpa Devharakar (shilpasd)
Changed in python-openstacksdk (Ubuntu):
status: New → In Progress
Revision history for this message
Matt Riedemann (mriedem) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.