Unhelpful error in the keystone log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Gage Hugo |
Bug Description
Occasionally an API (i.e. DELETE /v3/domains/
2017-09-12 23:20:37.995 7321 WARNING keystone.
No traceback. No other helpful messages as to what had caused the HTTP 500. With HTTP 500, I would expect a handsome looking traceback in the keystone log.
So diving into the code, I do see we log the exception if an unexpected error is raise.
https:/
But, if the error is exception.
https:/
Notice that expection.
https:/
So we have a couple of choices.
1. Find all the places where exception.
2. Add a couple of line of code here, https:/
Changed in keystone: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in keystone: | |
assignee: | nobody → Gage Hugo (gagehugo) |
status: | Triaged → In Progress |
Changed in keystone: | |
milestone: | none → queens-3 |
Reviewed: https:/ /review. openstack. org/526939 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=2be384b60c9 4e6e9d9cee7ee93 58ea886b6a193c
Committed: https:/
Submitter: Zuul
Branch: master
commit 2be384b60c94e6e 9d9cee7ee9358ea 886b6a193c
Author: Gage Hugo <email address hidden>
Date: Sun Dec 10 12:07:28 2017 -0600
Improve exception logging with 500 response
Currently when keystone throws a 500 Error, depending on the actual
exception type, it can log the message as an exception or as a warning.
Specifically, if the server throws an exception. UnexpectedError , it UnexpectedError .
does not log this as an exception; it simply logs it as a warning. This
patch set logs the error as an exception if exception.Error is an
exception.
Change-Id: Ia47cc11378ec64 d59b7403cb8a284 c764148d7a9
Co-Authored-By: Tin Lam <email address hidden>
Closes-Bug: #1717962