yahoo-eng-team team mailing list archive

[Scott Devoid <devoid@xxxxxxx>]

Public bug reported:

Example log in glance-api:
2014-07-02 14:01:33.850 27365 DEBUG glance.registry.client.v1.client [230e7f01-13eb-429f-81a3-88e55f883f2c 3e35b9d7f074420880e119472f7a234a 9d40160dbb0c48e4bb7cb29b6f125048] Registry request GET /images/detail HTTP 200 request id req-f750eea4-f52d-4a09-8a42-5e7aff066c43 do_request /usr/lib/py

As you can see, a req-UUID request ID comes in to glance-api, but when
it calls the glance registry client, it does not include the request ID
in that request. This makes it hard to track bugs going into glance and
into the registry.

** Affects: glance
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1336958

Title:
  glance-api calls to glance-registry should maintain request IDs

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  Example log in glance-api:
  2014-07-02 14:01:33.850 27365 DEBUG glance.registry.client.v1.client [230e7f01-13eb-429f-81a3-88e55f883f2c 3e35b9d7f074420880e119472f7a234a 9d40160dbb0c48e4bb7cb29b6f125048] Registry request GET /images/detail HTTP 200 request id req-f750eea4-f52d-4a09-8a42-5e7aff066c43 do_request /usr/lib/py

  As you can see, a req-UUID request ID comes in to glance-api, but when
  it calls the glance registry client, it does not include the request
  ID in that request. This makes it hard to track bugs going into glance
  and into the registry.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1336958/+subscriptions