yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #13704
[Bug 1309127] [NEW] The response error message from backend is not translated
Public bug reported:
When creating a subnet gets a failure, the output message includes an
error message from backend yet the error message is not translated.
I know it may not only a Horizon bug. At first, the error message from
backend is not translated. Second, I don't know if Horizon passes the
"Accept-Language" together with the request data to the backend. If the
backend service has supported lazy translation, it could accept a
parameter in HTTP header "Accept-Language", and response error messages
in the accepted language. So this issue needs both the back-end service
and Horizon to take a look together.
Regards
Daisy
** Affects: horizon
Importance: Undecided
Status: New
** Tags: i18n
** Attachment added: "The screen shot for this issue."
https://bugs.launchpad.net/bugs/1309127/+attachment/4086415/+files/error1.png
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1309127
Title:
The response error message from backend is not translated
Status in OpenStack Dashboard (Horizon):
New
Bug description:
When creating a subnet gets a failure, the output message includes an
error message from backend yet the error message is not translated.
I know it may not only a Horizon bug. At first, the error message from
backend is not translated. Second, I don't know if Horizon passes the
"Accept-Language" together with the request data to the backend. If
the backend service has supported lazy translation, it could accept a
parameter in HTTP header "Accept-Language", and response error
messages in the accepted language. So this issue needs both the back-
end service and Horizon to take a look together.
Regards
Daisy
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1309127/+subscriptions
Follow ups
References