Osprofiler works wrong

Bug #1789334 reported by pengdake
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Invalid
Undecided
Unassigned

Bug Description

I deploy Openstack Queen by rdo and enable osprofiler. But I can't get trace info from osprofiler.
For example:
1.run command like "# openstack --os-profile b827cb61b00c08648377fe889bf000d5 network show private"
2.get trace info by "# osprofiler trace show --connection-string elasticsearch://192.168.8.102:9200 --json 4a68f7fb-1f4b-4d04-bf93-7bfbd127fffa"

Trace with UUID 4a68f7fb-1f4b-4d04-bf93-7bfbd127fffa not found. Please check the HMAC key used in the command.

Config(/etc/neutron/neutron.conf):
[profiler]
enabled = True
trace_sqlalchemy = True
hmac_keys = XXXXX
connection_string = elasticsearch://192.168.8.102:9200

tags: added: troubleshooting
Revision history for this message
Slawek Kaplonski (slaweq) wrote :

It isn't neutron issue in fact. I checked that problem is with openstack sdk which is used by OSC for Neutron commands.
Bug is reported in https://storyboard.openstack.org/#!/story/2004618 and this one can be closed as invalid.

Changed in neutron:
status: New → Invalid
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.