Context's request-id not found in response of volume actions.

[Ibad Khan]

Majority of volume actions lack request-id whenever we have no data in response. Noticed that the actions return native webob.Response object because of which cinder's wsgi layer doesn't add context's response-id in the header.

wsgi block that decides whether to append response-id in header:
https://github.com/openstack/cinder/blob/master/cinder/api/openstack/wsgi.py#L906-L915

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/534363
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=745e84d5c4d3708ad2e71f49e4bcdb6f9fd30b54
Submitter: Zuul
Branch: master

commit 745e84d5c4d3708ad2e71f49e4bcdb6f9fd30b54
Author: Ibadulla Khan <email address hidden>
Date: Tue Jan 16 12:51:10 2018 +0530

    Fix: request-id missing in volume action's response header.

    Several volume actions use webob.Response object to
    return HTTP codes and cinder's wsgi layer doesn't append
    request-id if the actions return webob.Response object.

    If we intend to return certain HTTP code, we should use
    wsgi.response decorator and let cinder's wsgi layer create
    response object of it's own.

    Change-Id: Ibd6f60301e73022fecae4286e68d152bab73a40e
    Closes-Bug: 1743404

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/cinder 12.0.0.0rc1 release candidate.