)]}'
{"nova_powervm/virt/powervm/driver.py":[{"author":{"_account_id":9514,"name":"Brent Tang","email":"btang@us.ibm.com","username":"brenttang"},"change_message_id":"4bf9bf928a669be7e2a3219b1475580068232b11","unresolved":false,"context_lines":[{"line_number":1792,"context_line":"        except pvm_exc.VNCBasedTerminalFailedToOpen as err:"},{"line_number":1793,"context_line":"            LOG.error(_LE(\"Unable to open console.  Error is: %s\"),"},{"line_number":1794,"context_line":"                      err, instance\u003dinstance)"},{"line_number":1795,"context_line":"            raise exception.ConsoleNotAvailable()"},{"line_number":1796,"context_line":""},{"line_number":1797,"context_line":"        # Note that the VNC viewer will wrap the internal_access_path with"},{"line_number":1798,"context_line":"        # the HTTP content."}],"source_content_type":"text/x-python","patch_set":2,"id":"3ac371cc_106a3eee","line":1795,"range":{"start_line":1795,"start_character":35,"end_line":1795,"end_character":39},"updated":"2016-08-17 17:08:39.000000000","message":"This exception type needs to be \"ConsoleTypeUnavailable\" rather than \"ConsoleNotAvailable\"... The ConsoleNotAvailable is for the other type of remote consoles and so isn\u0027t handles through the VNC flow so is an uncaught exception.\n\nI think we should put a user-friendly string in the exception telling the user what the issue is otherwise it will just end up as \"Unavailable console type\" through the REST API... I did just try it out by doing \"raise exception.ConsoleTypeUnavailable(_(\u0027Test String\u0027))\" and I was able to get the Test String back through the REST API, so it seems to work to surface whatever is specified for the message (which overrides the default message format.","commit_id":"c0fea5c73a372367cd0d05b2d3c205f9c9a5f7c6"}]}