Bug 836507 - unclear error message "Command XYZ failed"
unclear error message "Command XYZ failed"
Status: NEW
Product: Beaker
Classification: Community
Component: inventory (Show other bugs)
0.9
Unspecified Unspecified
medium Severity medium (vote)
: ---
: ---
Assigned To: beaker-dev-list
tools-bugs
UX
: FutureFeature, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-29 06:01 EDT by Ales Zelinka
Modified: 2016-10-24 19:47 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Comment 3 Roman Joost 2016-10-24 19:46:50 EDT
We've talked about this today, and tweaking the error message does not really make it easier to understand.

Ideas:

* Since Beaker now features and Installation tab, we could provide a way to put a better understandable message in the tab to explain why the installation had failed.
* In order to figure out the cause for the error message, Beaker keeps records during the installation which can be queried from the database.
* UI idea: place the error message next to the timestamp which would normally say the status report (e.g. Netboot configured). Maybe add an icon as well if suitable.

Note You need to log in before you can comment on or make changes to this bug.