)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"8584fed986d3dfb174242a2130aeeeeae87bc3e3","unresolved":false,"context_lines":[{"line_number":19,"context_line":"auth_type option.  But this is a pretty good first indicator that the"},{"line_number":20,"context_line":"admin forgot to populate auth options in general."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"[1] http://paste.openstack.org/show/623721/"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Change-Id: Ife1d26fd2373a02fc4f7f1bbffa7ec052457f11e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"5f4e5783_50685d1b","line":22,"updated":"2017-10-17 11:58:02.000000000","message":"Does this warrant an associated bug for bookkeeping etc? Or, if this is associated strongly enough with the ksa work you\u0027ve done, perhaps horking it on to that blueprint?","commit_id":"88b8e4a3ad1ce9030714d7d7f68a32b0aa0eb501"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"b4e6226b6fb03cd11a99067ae6de4ab381a4e95f","unresolved":false,"context_lines":[{"line_number":19,"context_line":"auth_type option.  But this is a pretty good first indicator that the"},{"line_number":20,"context_line":"admin forgot to populate auth options in general."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"[1] http://paste.openstack.org/show/623721/"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Change-Id: Ife1d26fd2373a02fc4f7f1bbffa7ec052457f11e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3f4b6375_401e010d","line":22,"in_reply_to":"5f4e5783_50685d1b","updated":"2017-10-18 21:34:54.000000000","message":"Opened bug #1724689 (niraj_singh was supposed to do that, as he discovered the issue, but I don\u0027t think that happened).\n\nNo, this has nothing to do with the KSA work.","commit_id":"88b8e4a3ad1ce9030714d7d7f68a32b0aa0eb501"}],"nova/exception.py":[{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"8584fed986d3dfb174242a2130aeeeeae87bc3e3","unresolved":false,"context_lines":[{"line_number":2181,"context_line":"    msg_fmt \u003d _(\"The trait %(name)s is in use by a resource provider.\")"},{"line_number":2182,"context_line":""},{"line_number":2183,"context_line":""},{"line_number":2184,"context_line":"class ServiceUserTokenNoAuth(NovaException):"},{"line_number":2185,"context_line":"    msg_fmt \u003d _(\"The [service_user]send_service_user_token option was \""},{"line_number":2186,"context_line":"                \"requested, but no service auth could be loaded. Please check \""},{"line_number":2187,"context_line":"                \"the [service_user] configuration section.\")"}],"source_content_type":"text/x-python","patch_set":2,"id":"5f4e5783_509bbd16","line":2184,"updated":"2017-10-17 11:58:02.000000000","message":"Who/what is going to see this exception? If it is going to bubble out to the API, is this information of any use to the caller, or is it only to be of use to the operator of the cloud?","commit_id":"88b8e4a3ad1ce9030714d7d7f68a32b0aa0eb501"},{"author":{"_account_id":14070,"name":"Eric Fried","email":"openstack@fried.cc","username":"efried"},"change_message_id":"b4e6226b6fb03cd11a99067ae6de4ab381a4e95f","unresolved":false,"context_lines":[{"line_number":2181,"context_line":"    msg_fmt \u003d _(\"The trait %(name)s is in use by a resource provider.\")"},{"line_number":2182,"context_line":""},{"line_number":2183,"context_line":""},{"line_number":2184,"context_line":"class ServiceUserTokenNoAuth(NovaException):"},{"line_number":2185,"context_line":"    msg_fmt \u003d _(\"The [service_user]send_service_user_token option was \""},{"line_number":2186,"context_line":"                \"requested, but no service auth could be loaded. Please check \""},{"line_number":2187,"context_line":"                \"the [service_user] configuration section.\")"}],"source_content_type":"text/x-python","patch_set":2,"id":"3f4b6375_407a8124","line":2184,"in_reply_to":"5f4e5783_509bbd16","updated":"2017-10-18 21:34:54.000000000","message":"I think the compute service will blow up and the message will be in the compute log.  That\u0027s appropriate, since there\u0027s nothing the end user would be able to do about it.  The operator needs to take action (namely correcting the config and restarting the compute service).  I kinda doubt this would get all the way to the end user anyway, since something would hit this pretty early and blow up the service before any serious work could be attempted.","commit_id":"88b8e4a3ad1ce9030714d7d7f68a32b0aa0eb501"}]}