Ask Your Question
0

osprofiler "something has gone wrong"

asked 2017-04-09 04:59:41 -0500

Bernd Bausch gravatar image

updated 2017-04-09 06:09:24 -0500

I want to try Osprofiler on Packstack/Ocata:

$ source demo
$ cinder --profile osprofiler-secret create 1
...
To display trace use next command:
osprofiler trace show --html 8871c235-7337-4e14-a81c-0c83e404c74f
$ source admin
$ osprofiler trace show --html 8871c235-7337-4e14-a81c-0c83e404c74f
Something has gone wrong. See ceilometer logs for more details

This error message is generated in osprofiler/drivers/ceilometer.py when osprofiler fails to retrieve the ceilometer client. Not surprisingly, there is no trace in the ceilometer logs. Can I fix this? How?

EDIT I added code to the osprofiler command to print exception details. This is what I get:

$ osprofiler trace show 8b62c09d-ba71-4ea6-8f77-694aa7b58381
Exception:
Authentication failed. Missing options: token, endpoint, tenant_id, tenant_name
Something has gone wrong. See ceilometer logs for more details

The ceilometer client wants authentication. What can I do to satisfy it?

EDITthere is a four-months old bug https://bugs.launchpad.net/osprofiler...

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-04-09 06:28:11 -0500

Bernd Bausch gravatar image

I solved this particular problem by adding --os-tenant-name PROJECT_NAME to the osprofiler command. As a result, I get a different error now, for which I open another question.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-04-09 04:59:41 -0500

Seen: 53 times

Last updated: Apr 09