Cinder

Missing global request ID in non API services

Bug #1743462 reported by Gorka Eguileor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Gorka Eguileor

Bug Description

Cinder doesn't propagate global request IDs internally, so any external request that comes with it will have it logged at the API service and then we'll lose this information in all the other services.

Gorka Eguileor (gorka)
Changed in cinder:
assignee: nobody → Gorka Eguileor (gorka)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

Changed in cinder:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/533793
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=28ada504af4084f72f3503d77806075e7ad509b0
Submitter: Zuul
Branch: master

commit 28ada504af4084f72f3503d77806075e7ad509b0
Author: Gorka Eguileor <email address hidden>
Date: Mon Jan 15 21:47:56 2018 +0100

    Fix: Propagate OS global request ID

    Cinder doesn't propagate global request IDs internally, so any external
    request that comes with it will have it logged at the API service and
    then we'll lose this information in all the other services.

    We are properly serializing this information on our RPC calls, but we
    are not reconstructing the Context properly on the receiving end.

    This patch ensures that the "global_request_id" field from the context
    is properly added on RPC reception.

    Closes-Bug: #1743462
    Change-Id: I35834a43298b5287d5cd3c37baa82903bdffda12

Changed in cinder:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/537326

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 12.0.0.0b3

This issue was fixed in the openstack/cinder 12.0.0.0b3 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (stable/pike)

Reviewed: https://review.openstack.org/537326
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=d9b38a4b23c21b92ed1c3a86a6201bd94c644c3d
Submitter: Zuul
Branch: stable/pike

commit d9b38a4b23c21b92ed1c3a86a6201bd94c644c3d
Author: Gorka Eguileor <email address hidden>
Date: Mon Jan 15 21:47:56 2018 +0100

    Fix: Propagate OS global request ID

    Cinder doesn't propagate global request IDs internally, so any external
    request that comes with it will have it logged at the API service and
    then we'll lose this information in all the other services.

    We are properly serializing this information on our RPC calls, but we
    are not reconstructing the Context properly on the receiving end.

    This patch ensures that the "global_request_id" field from the context
    is properly added on RPC reception.

    Closes-Bug: #1743462
    Change-Id: I35834a43298b5287d5cd3c37baa82903bdffda12
    (cherry picked from commit 28ada504af4084f72f3503d77806075e7ad509b0)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 11.1.0

This issue was fixed in the openstack/cinder 11.1.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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