Make error messages friendly and useful.

Registered by Christopher MacGown on 2011-07-08

While at an openstack hackathon, an new user of OpenStack complained that the error messages were too cryptic since they were often just stacktraces. Each openstack project should capture all typical configuration mistakes, errors, etc., and ensure that they provide useful and friendly error messages, both at console and in the logs. E.g., indicating missing packages, missing or mis-configured network links, permission errors, etc.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.