Description of problem:
Horizon is reporting Incorrect error message if try to startup a VM that is LOCKED
message "Unable to start instance <instance-name>" which looks very general & no clue of what is wrong.
Command line & logs reporting correct error so need correction for horizon
2017-03-15 13:12:47.668 4727 INFO nova.api.openstack.wsgi [req-f9d76dae-9937-447b-87b9-22ec9c5111ca 2df09339b160462d82994c4554c6a321 ceb3659d22a7467693a720a2cf62fcce - - -] HTTP exception thrown: Instance bf5ac469-6c50-43d8-aa09-7d6be59a8c2b is locked
[root@controller ~(keystone_admin)]# nova start vm-user1
Instance bf5ac469-6c50-43d8-aa09-7d6be59a8c2b is locked (HTTP 409) (Request-ID: req-50b222ba-4e2d-43a3-b9c8-74d04219a388)
ERROR (CommandError): Unable to start the specified server(s).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
horizon should report "<instance> is locked - unlock first"
The idea is that you check the logs to see what is wrong exactly. Horizon is supposed to be a frontend for the users of the cloud, and not a debugging tool for its operators. We can't simply forward every error message to the user, because we are never sure if it contains some technical details that the user shouldn't have access to, and because it's not translated.
*** Bug 1432404 has been marked as a duplicate of this bug. ***
There is upstream work on that.
The upstream patch has merged.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.