Context's request-id not found in response of volume actions.
Bug #1743404 reported by
Ibad Khan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
Ibad Khan |
Bug Description
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:/
Changed in cinder: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in cinder: | |
assignee: | nobody → Ibad Khan (ik-ibadkhan) |
status: | Confirmed → New |
summary: |
- Context response-id not found in response of volume actions. + Context's request-id not found in response of volume actions. |
description: | updated |
Changed in cinder: | |
status: | New → In Progress |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/534363
Review: https:/