Error messages do not convey problem or resolution

[Victoria Kouyoumjian]

Error messages frequently do not indicate why the error occurred or how the user should address the problem to avoid the error.

[Victoria Martinez de la Cruz (vkmc)]

Agree. We should improve error messages to be more detailed for usability reasons. This may require some work (there are several errors to enhance), so probably is better to submit a blueprint.

[Akihiro Motoki (amotoki)]

Agree with both the bug report and a point that it is better to be improved as a blueprint. Error message should provide the reason of error for a user to address the problem.

In addition to add a reason to each error message, we need to consider how to provide translated error message. Just adding a reason leads to a situation that english and translated strings are mixed. Of course, this is a separate issue.

[Juan Manuel Ollé (juan-m-olle)]

This issue is an specific case of this one

https://bugs.launchpad.net/horizon/+bug/1261755

In this case (in my opinion descripted in the comments) other modules than horizon must be modify

[Juan Manuel Ollé (juan-m-olle)]

Sorry, the other is an specific case of this one

[Gary W. Smith (gary-w-smith)]

This concern is being addressed by https://blueprints.launchpad.net/horizon/+spec/improve-error-message-details-for-usability

[Richard Jones (r1chardj0n3s)]

This bug report is far too vague to be useful. Please note specific instances of messages that could be fixed.

[hanjiabao (hanjiabao)]

i would say that we should split this bug into some parts,that would be easier

[Launchpad Janitor (janitor)]

[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]