)]}'
{"tempest/common/rest_client.py":[{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"b094484657453e5e379bb9b2266b360ae3d71a89","unresolved":false,"context_lines":[{"line_number":514,"context_line":"                elif \u0027computeFault\u0027 in resp_body:"},{"line_number":515,"context_line":"                    message \u003d resp_body[\u0027computeFault\u0027][\u0027message\u0027]"},{"line_number":516,"context_line":"                elif \u0027error\u0027 in resp_body:  # Keystone errors"},{"line_number":517,"context_line":"                    try:"},{"line_number":518,"context_line":"                        message \u003d resp_body[\u0027error\u0027][\u0027message\u0027]"},{"line_number":519,"context_line":"                    except TypeError:"},{"line_number":520,"context_line":"                        # NOTE(afazekas): The \u0027error\u0027 likely an str"}],"source_content_type":"text/x-python","patch_set":1,"id":"AAAATn%2F%2F%2BpU%3D","line":517,"updated":"2013-10-24 11:14:40.000000000","message":"I don\u0027t think we should be solving this with a try catch. It looks like previously this was specifically designed to do keystone errors. But neutron errors have yet another error format. So that should be looked at in the body (ideally we\u0027d have some way of knowing in advance).","commit_id":"dd3e315ef7d0e5d4184975f43de92c743124b2eb"}]}