Bug 877959 - [ru_RU][SAM Web GUI] - Upload New Manifest showing error messages improperly.
[ru_RU][SAM Web GUI] - Upload New Manifest showing error messages improperly.
Product: Subscription Asset Manager
Classification: Red Hat
Component: katello (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Tom McKay
: i18n
Depends On:
Blocks: sam12-tracker
  Show dependency treegraph
Reported: 2012-11-19 05:31 EST by Satyabrata Maitra
Modified: 2012-11-30 10:56 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-11-30 10:56:59 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Errorneously showing error messages, contains coding. (77.53 KB, image/png)
2012-11-19 05:31 EST, Satyabrata Maitra
no flags Details

  None (edit)
Description Satyabrata Maitra 2012-11-19 05:31:53 EST
Created attachment 647669 [details]
Errorneously showing error messages, contains coding.

Description of problem:
In ru_RU locale, to import manifest, when trying to upload new manifest file (may it is not a proper manifest file or some other file) through browse, it is showing an Argument Error. First of all it is showing in en_US locale and at the same time it is showing another error message which contains the code, instead of pure sentence based error message.

Version-Release number of selected component (if applicable):
Subscription Asset Manager Version: 1.2.5-1h.el6_3

How reproducible:

Steps to Reproduce:
1. Login with ru_RU locale.
2. Go to Contents tab
3. Click on Import Manifest
4. Click on Browse, on the "Upload New manifest" field.
5. Try to upload just any file.
6. Observe the error messages showing.
Actual results:
The Erroneous error message showing which contains codes.

Expected results:
It should show the error message more meaningfully, in sentence, not having any coding in it.

Additional info: Screen shot attached for reference.
Comment 1 Tom McKay 2012-11-30 10:56:59 EST
The cause of this error is fixed in a newer compose. The error message itself, being from a backend engine, will not be translated.

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