RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 627830 - [ALL LANG] failure to rhn registration message is preferred to be translated
Summary: [ALL LANG] failure to rhn registration message is preferred to be translated
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rhn-client-tools
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-27 04:58 UTC by Kenichi Takemura
Modified: 2014-08-04 22:03 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-09 19:43:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screen shot of rhn-register (156.32 KB, image/png)
2010-08-27 04:58 UTC, Kenichi Takemura 		no flags Details
View All

Description Kenichi Takemura 2010-08-27 04:58:35 UTC 
Created attachment 441401 [details]
Screen shot of rhn-register

Description of problem:

Failure of registering a system to rhn due to the exhaustion of subscriptions shows an error message in English.

I think this message is preferred to be translated for customers can understand they need to remove their system. 

Version-Release number of selected component (if applicable):
RHEL6.0-20100818.0(Snap12)

How reproducible:
Always

Steps to Reproduce:
Steps are one of
1. Install rhel6
1. Run firstboot 
1. Run rhn_register
  
Actual results:
See attached.

Expected results:
Message is translated.

Additional info:
I tried ko_KR but it appears all lang does not have translated message.
Comment 2 Noriko Mizumoto 2010-08-31 02:25:23 UTC 
After searching in ja.po of firstboot, there are no such words 'RHN' or 'register' contained.
It can be inferred in two situation. 
One: The error message is contained some other package, but not firstboot. 
Two: The error message is not provided in PO file for translation. 

Can you try some other European language as well, such as de, fr and es?
Comment 3 Manuel Ospina 2010-08-31 03:33:32 UTC 
I also check rhn_client. The "Problem registering system" is translated. The other strings (Error Class Info and Explanation) are not in the files. If this is happening in all the languages, I believe this strings are not marked for translation
Comment 4 Kenji Nanamiya 2010-08-31 06:06:45 UTC 
Manuel,
Is it possible for you to include these error class codes information in your translation lists? They are messages to notify customers the cause of the error, so if they read this message, they can rectify the situation in most of cases. Usually it does not contain user specific information.
Thanks,
Kenji
Comment 5 Kenichi Takemura 2010-08-31 06:34:51 UTC 
I tested following languages and none of them have translated messages.
I do not think this is marked for translation.

 Japanese (ja_JP)
 Korean (ko_KR) 
 Chinese (Simplified) 	 
 Chinese (Traditional)
 Portuguese (Brazilian) 
 French (fr_FR) 
 German (de_DE) 
 Italian (it_IT) 
 Russian (ru_RU) 
 Spanish (es_ES) 
 Assamese (as_IN)
 Bengali (bn_IN)  

If package is rhn-client-tools, package owner is 'msuchy'
Comment 6 A S Alam 2010-08-31 06:50:40 UTC 

*** This bug has been marked as a duplicate of bug 626343 ***
Comment 7 A S Alam 2010-08-31 07:04:35 UTC 
Duplicate->Assigned
Comment 8 Ankit Patel 2010-08-31 12:07:56 UTC 
After some research, I realized that there are actually three different bugs.

1. Messages translated from rhn-client-tools are not showing translated. e.g. attachment #440342 [details] and attachment #440343 [details] from bug #626343 shows the messages that are already translated and available under rhn-client-tools.

2. Messages untranslated and needs to be translated under spacewalk-server component, from the attachment #441401 [details] from this bug (bug #627830).
https://translate.fedoraproject.org/projects/p/spacewalk/c/spacewalk-server/view/backend/po/server.pot

However, I am not sure against which component the bug has to be filed?
a) spacewalk -> server OR
b) spacewalk -> client OR
c) some RHEL6 component

3. Message ("The login or password is incorrect") shown in the attachment #440341 [details] from bug #626343 is not available under spacewalk-server, rather "3: _("This login is already taken, or the password is incorrect.")" is available from satellite/backend/common/rhnException.py

For all three of the above issues we will need satellite team's help as well as i18n team's help. and all of them requires separate bugs I believe.

Aalam/Kenichi, could you please file new bugs?

Thanks!
Ankit
Comment 9 Jan Pazdziora 2010-11-23 13:46:56 UTC 
The English message comes straight from RHN / RHN Satellite. We won't be able to address this on RHEL 6 client side.
Comment 10 Ankit Patel 2010-12-06 09:17:40 UTC 
(In reply to comment #9)
> The English message comes straight from RHN / RHN Satellite. We won't be able
> to address this on RHEL 6 client side.

Hi Jan,

So what should be the solution to fix this issue?

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