There are more than one trace_id

Bug #1791638 reported by pengdake
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
osprofiler
New
Undecided
Unassigned

Bug Description

My openstack version is Queens and osprofiler version is 1.15.2.

I found there are two trace_ids on different openstack services.

The service about api always gets current trace_id, but other service gets old trace_id.

For example, I get trace_id by osprofiler.profiler.get().get_base_id() on nova-api and nova-compute.

nova-api:
[root@localhost ~(keystone_admin)]# nova-api
success to get base_id: d9247f1c-65e9-4017-9461-2781fde381c5 (current trace_id)

nova-compute:
[root@localhost ~]# nova-compute
success to get base_id: 73a59ef0-f0c2-4fb4-8046-b729af1f2e22 (old trace_id)

Revision history for this message
Thomas Bechtold (toabctl) wrote :

Can you describe the steps and configurations that are needed to reproduce this problem please?

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.