This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2076914 - Untranslated error messages from exceptions in D-Bus calls
Summary: Untranslated error messages from exceptions in D-Bus calls
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: subscription-manager
Version: 9.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Pino Toscano
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-20 08:19 UTC by Lijun Li
Modified: 2023-09-22 13:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-22 13:55:55 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github candlepin candlepin pull 3349 0 None Merged 2076914: Translate few strings. 2022-11-25 17:22:23 UTC
Github candlepin subscription-manager-cockpit pull 23 0 None Merged Translate few error messages 2022-11-25 17:22:24 UTC
Github candlepin subscription-manager pull 3058 0 None closed 2076914: Translate two error messages 2022-11-25 17:22:24 UTC
Red Hat Issue Tracker ENT-5527 0 None None None 2022-11-25 17:22:03 UTC
Red Hat Issue Tracker   RHEL-7159 0 None Migrated None 2023-09-22 13:55:57 UTC
Red Hat Issue Tracker RHELPLAN-119372 0 None None None 2022-04-20 08:28:33 UTC

Description Lijun Li 2022-04-20 08:19:33 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Open RHSM Cockpit Client via click Applications - System Tools - Red Hat Subscription Manager on the top menu bar from desktop.
2. Click Register button in Subscriptions dialog box, and check the pop-up Register System dialog box.
3. Select Custom URL and input stage env URL.
4. Check/uncheck 'Use proxy server', 'Attach automatically' or 'Connect this system to Red Hat Insights' checkbox.
5. Select Account or Activation Keys for Method, check the Login validation, and then input the correct Username and Password.
6. Click Register button.

Actual results:
[ALL LANG][RHSM Cockpit Client][RHSM Cockpit] Unlocalized warning messages in Register System dialog box:
Unable to connect to: test:3128 [Errno -2] 
Error: 'Organization' is required when using activation keys...
Invalid credentials.


Expected results:
They should be localized.

Additional info:
Please see the attached screen-shot.
Comment 2 Pino Toscano 2022-04-20 12:54:39 UTC 
Regarding the three error messages:
1) "Unable to connect to: test:3128 [Errno -2]"
2) "Error: 'Organization' is required when using activation keys..."
3) "Invalid credentials."

(1) seems to be a raw ProxyException string in sub-man, apparently something is missing to handle it properly (and provide a better user explanation).

(2) seems to be an untranslated error string in the cockpit plugin itself (subscriptions-client.js).

(3) seems to be a raw NotAuthorizedException in Candlepin itself.
Comment 3 Pino Toscano 2022-05-26 12:18:35 UTC 
The cockpit parts (In reply to Pino Toscano from comment #2)
> (2) seems to be an untranslated error string in the cockpit plugin itself
> (subscriptions-client.js).

This will be hopefully fixed with
https://github.com/candlepin/subscription-manager-cockpit/pull/23
Comment 5 Pino Toscano 2022-07-08 07:27:45 UTC 
To recap the situation a bit after changes here and there:

(In reply to Pino Toscano from comment #2)
> 1) "Unable to connect to: test:3128 [Errno -2]"
>
> (1) seems to be a raw ProxyException string in sub-man, apparently something
> is missing to handle it properly (and provide a better user explanation).

This still needs to be addressed in subscription-manager; most likely it will need the fixes for bug 1971995 to be effective.

(In reply to Pino Toscano from comment #2)
> 2) "Error: 'Organization' is required when using activation keys..."
>
> (2) seems to be an untranslated error string in the cockpit plugin itself
> (subscriptions-client.js).

This was already fixed in subscription-mananger-cockpit;
in particular, subscription-mananger-cockpit-2-1 (in RHEL 9.1 nightlies) already has this fix.

(In reply to Pino Toscano from comment #2)
> 3) "Invalid credentials."
> 
> (3) seems to be a raw NotAuthorizedException in Candlepin itself.

This was fixed in upstream Candlepin already.
IIRC a new version of Candlepin should be rolled in production pretty soon, and thus should also bring the "Invalid credentials" message translated at least into fr, ja, ko, uk, zh_CH.

=====

Because of this, I'm keeping this bug open for subscription-manager, giving it a slightly more clear title on what's left to do, and moving it back to NEW (since it is not currently being worked on).
Comment 6 Lijun Li 2022-09-19 02:04:30 UTC 
It's reproduced in latest RHEL9.1 build as well.
Comment 8 Lijun Li 2023-04-25 06:52:49 UTC 
Reproduced on latest RHEL9.2 build.
Comment 9 Lijun Li 2023-04-25 07:00:55 UTC 
Unlocalized messages:
Proxy error at test:3128: [Errno -2] 
Invalid credentials.
Comment 10 Pino Toscano 2023-04-25 07:15:59 UTC 
(In reply to Lijun Li from comment #9)
> Invalid credentials.

This message existed in Candlepin before version 4.2.3, and subscription.rhsm.redhat.com currently runs 4.2.15 which has "Invalid Credentials" (different casing, no period at the end). "Invalid Credentials" existed for a long time, and it was already translated in Japanese and Chinese (and some other languages).
So:
- which registration server are you trying to register against?
- are you really sure the message you get is "Invalid credentials." and not "Invalid Credentials"?
- can you please add an extra screenshot (not the whole screen, only the registration popup in cockpit is enough) of the issue?

Thanks!
Comment 11 Lijun Li 2023-04-25 08:00:29 UTC 
(In reply to Pino Toscano from comment #10)
> (In reply to Lijun Li from comment #9)
> > Invalid credentials.
> 
> This message existed in Candlepin before version 4.2.3, and
> subscription.rhsm.redhat.com currently runs 4.2.15 which has "Invalid
> Credentials" (different casing, no period at the end). "Invalid Credentials"
> existed for a long time, and it was already translated in Japanese and
> Chinese (and some other languages).
> So:
> - which registration server are you trying to register against?
Stage server: subscription.rhsm.stage.redhat.com

> - are you really sure the message you get is "Invalid credentials." and not
> "Invalid Credentials"?
It's "Invalid Credentials".

> - can you please add an extra screenshot (not the whole screen, only the
> registration popup in cockpit is enough) of the issue?
Please see the attached screenshot.

> 
> Thanks!
Comment 13 Pino Toscano 2023-04-25 08:39:51 UTC 
(In reply to Lijun Li from comment #11)
> (In reply to Pino Toscano from comment #10)
> > (In reply to Lijun Li from comment #9)
> > > Invalid credentials.
> > 
> > This message existed in Candlepin before version 4.2.3, and
> > subscription.rhsm.redhat.com currently runs 4.2.15 which has "Invalid
> > Credentials" (different casing, no period at the end). "Invalid Credentials"
> > existed for a long time, and it was already translated in Japanese and
> > Chinese (and some other languages).
> > So:
> > - which registration server are you trying to register against?
> Stage server: subscription.rhsm.stage.redhat.com
> 
> > - are you really sure the message you get is "Invalid credentials." and not
> > "Invalid Credentials"?
> It's "Invalid Credentials".
> 
> > - can you please add an extra screenshot (not the whole screen, only the
> > registration popup in cockpit is enough) of the issue?
> Please see the attached screenshot.

Do you get the same issue when trying to register to the same server and same wrong credentials on console using `subscription-manager`?
Comment 14 Lijun Li 2023-04-25 08:55:09 UTC 
(In reply to Pino Toscano from comment #13)
> (In reply to Lijun Li from comment #11)
> > (In reply to Pino Toscano from comment #10)
> > > (In reply to Lijun Li from comment #9)
> > > > Invalid credentials.
> > > 
> > > This message existed in Candlepin before version 4.2.3, and
> > > subscription.rhsm.redhat.com currently runs 4.2.15 which has "Invalid
> > > Credentials" (different casing, no period at the end). "Invalid Credentials"
> > > existed for a long time, and it was already translated in Japanese and
> > > Chinese (and some other languages).
> > > So:
> > > - which registration server are you trying to register against?
> > Stage server: subscription.rhsm.stage.redhat.com
> > 
> > > - are you really sure the message you get is "Invalid credentials." and not
> > > "Invalid Credentials"?
> > It's "Invalid Credentials".
> > 
> > > - can you please add an extra screenshot (not the whole screen, only the
> > > registration popup in cockpit is enough) of the issue?
> > Please see the attached screenshot.
> 
> Do you get the same issue when trying to register to the same server and
> same wrong credentials on console using `subscription-manager`?

Yes, but the message not the same on CLI console, please see as below.

# subscription-manager register 
登録中: subscription.rhsm.stage.redhat.com:443/subscription
ユーザー名: test
パスワード: 
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html (HTTP エラーコード 401: Unauthorized)
^^^^^^^^^^^^^^^^^^^^^^^ Not "Invalid Credentials"^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Comment 15 Pino Toscano 2023-04-26 08:18:52 UTC 
(In reply to Lijun Li from comment #11)
> > - can you please add an extra screenshot (not the whole screen, only the
> > registration popup in cockpit is enough) of the issue?
> Please see the attached screenshot.

From the screenshot, it looks like both username and password were empty - is that correct?
If so, I'd try to use the same invalid credentials you used in CLI (comment 14).
Comment 16 Lijun Li 2023-04-26 08:26:28 UTC 
(In reply to Pino Toscano from comment #15)
> (In reply to Lijun Li from comment #11)
> > > - can you please add an extra screenshot (not the whole screen, only the
> > > registration popup in cockpit is enough) of the issue?
> > Please see the attached screenshot.
> 
> From the screenshot, it looks like both username and password were empty -
> is that correct?
> If so, I'd try to use the same invalid credentials you used in CLI (comment
> 14).

Yes correct, they were just empty.
Comment 17 RHEL Program Management 2023-05-31 07:28:14 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 20 RHEL Program Management 2023-09-22 13:55:25 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 21 RHEL Program Management 2023-09-22 13:55:55 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.