Red Hat Bugzilla – Bug 895586
RFE: Display more information on cause of instance error state on UI
Last modified: 2016-04-26 15:28:55 EDT
Description of problem:
When creating an instance fails no user-actionable feedback is displayed in the UI.
- The status of the instance updates to "Error".
- Clicking through to the instance overview yields no additional information.
- Clicking the logs tab yields no logs.
As a result when an instance fails to start the user's only recourse is to head to the command line and use nova show (and even that is a bit of a hit and miss affair, see Bug #891051).
The cause for the failure to create the instance should be made visible via the UI.
Agreed, although Horizon can only display whatever information is returned by the nova API.
(In reply to comment #1)
> Agreed, although Horizon can only display whatever information is returned
> by the nova API.
My understanding based on the below is that some more information to this end is available from Nova in Grizzly:
As part of launchpad bug 1236168 (merged in Icehouse M1), Horizon now shows an error message when failing to launch an instance (what you would get with 'nova show'). We probably still want to at least add this info to the Instances Details page, though.
*** Bug 1033141 has been marked as a duplicate of this bug. ***
Note the previously linked patch was merged into Icehouse-1 and adds information about the error to the Instance Details page (as shown by `nova show <instance id>`).
Attaching sfdc ticket 01080752 to track when RFE is complete
This should already be available in the current RHEL OSP 5 packages, updating status.
Created attachment 910250 [details]
verified on python-django-horizon-2014.1-7.el7ost.noarch.
curreent error shows the short description + the http error code + related error.
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.