Bug 1026113

Summary: [ALL_LANG] Unlocalized error message: Project -> Access & Security -> Keypairs -> Create Keypair
Product: Red Hat OpenStack Reporter: Yuko Katabami <ykatabam>
Component: python-django-horizonAssignee: Matthias Runge <mrunge>
Status: CLOSED CURRENTRELEASE QA Contact: Shai Revivo <srevivo>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.0CC: aortega, athomas, iovadia, lijli, mkaliyam, mrunge, nbarcet, qe-i18n-bugs, srevivo, ykatabam
Target Milestone: ---Keywords: i18n, Triaged
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-12 20:47:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Unlocalized error message for Create Keypair
none
error message localized in ja-JP none

Description Yuko Katabami 2013-11-03 22:12:05 UTC
Description of problem:
Error message shown when failed to create keypair is not fully localized.
The part of the message after "Error: Unable to create keypair." is unlocalized and does not exist in the current upstream file.

Version-Release number of selected component (if applicable): 4.0


How reproducible: 100%


Steps to Reproduce:

1. Log in to Dashboard as admin user. 
2. Click "Settings" and change the language setting other than English.
3. On the left panel, select "Project" tab and click "Access & Security" from the menu.
4. On the main panel, click "Keypairs" tab.
5. Click "Create Keypair".

Actual results:
If "Create" action fails, it shows an error message which is not fully localized:

エラー: キーペアを作成できません。Key pair 'xxx' already exists. (HTTP 409)
(Request-ID: req-23cf2f19-dce2-4d06-b3fe-b9b32d32e68e)

Expected results:
It should be fully localized.

Additional info:
Screenshot attached.
Please note that the steps to reproduce described above does not always work.

Comment 1 Yuko Katabami 2013-11-03 22:13:15 UTC
Created attachment 818831 [details]
Unlocalized error message for Create Keypair

Comment 3 Yuko Katabami 2013-11-03 22:29:45 UTC
Just realized that in order to reproduce this error message, you simply create one keypair and then try to make another one using the same name.

Comment 4 Julie Pichon 2013-11-12 14:52:50 UTC
Thank you for the bug report.

Horizon is displaying the error message as it is returned by the Nova compute service. There are two issues at hand here: Nova strings are not translated, and there is no good system currently to request for a message to be returned in a specific locale. Fixing this will require a larger effort together with the other projects.

Comment 5 Julie Pichon 2014-10-07 13:13:52 UTC
Nova now appears to support the Accept-Language header: https://blueprints.launchpad.net/nova/+spec/user-locale-api . I will create a blueprint upstream for Horizon to take advantage of this - it's larger than just this bug, we should use the header with every API that supports it (I know at least Cinder does). I'll post a link back here once the blueprint is created.

Because feature freeze was on September 4th this won't make Juno / 6.0. I'll retarget to 7.0 when it's added to the "target release" dropdown.

Comment 8 Masco 2015-12-21 12:21:50 UTC
The workflow is changed. now the error is displaying during validation time only.
so we can't reproduce in latest releases.

upstream change ids:
I223c963349fe65ca09ed805edeebbe234c0131dc
I5f543063aa3bc90824299b53f18123bac000348e

Comment 9 Matthias Runge 2016-01-14 09:58:59 UTC
Yuko,

as Masco stated in his comment, the workflow was changed for liberty release. Could you please retry this on RHOS-8?

Thank you,
Matthias

Comment 10 Yuko Katabami 2016-01-14 10:29:10 UTC
Hi Matthias,

Would it be possible for you to provide me a test environment, so I can check it?
I only have horizon osp-7 at the moment.

Comment 13 Yuko Katabami 2016-04-07 09:28:59 UTC
Created attachment 1144637 [details]
error message localized in ja-JP

I have checked with osp-8 Horizon and confirmed that the error message is now localized.
Moving the status to VERIFIED.