Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 888865[details]
RHEL7 rhn-client-tools inconsistency
Description of problem:
Registration procedure of RHEL7 machine against Satellite 5.6 (or Proxy 5.6) using rhn-client-tools TUI and GUI tools seems to be a bit inconsistent. The strings and messages displayed both in GUI and TUI are saying (almost) the same but usually in quite a different way (sometimes confusing/ed), which leads to doubled effort of the documentation team and harder sustainability of the code itself.
Ideally, all the (rhn-client-tools) strings should be stored at one place together with the translations and GUI and TUI tools should include these strings.
See the attached pdf with highlighted differences between TUI and GUI.
Version-Release number of selected component (if applicable):
rhn-client-tools-2.0.2-5.el7
How reproducible:
always
Steps to Reproduce:
1. provision RHEL7 guest (with English locale)
2. register the guest against Satellite 5.6 using TUI rhn-client-tools (rhn_register --nox)
3. register the guest against Satellite 5.6 using GUI rhn-client-tools (rhn_register)
Actual results:
Messages and strings are mostly different and inconsistent, sometimes confusing or confused, containing some typos and grammar mistakes, usually saying almost the same, but in a quite different way, hence we double the translation team effort.
Expected results:
GUI and TUI messages and strings and the workflow are the same and unified with the same options (in TUI we cannot specify Proxy details, while in GUI we cannot specify the SSL cert path).
Additional info:
Created attachment 888865 [details] RHEL7 rhn-client-tools inconsistency Description of problem: Registration procedure of RHEL7 machine against Satellite 5.6 (or Proxy 5.6) using rhn-client-tools TUI and GUI tools seems to be a bit inconsistent. The strings and messages displayed both in GUI and TUI are saying (almost) the same but usually in quite a different way (sometimes confusing/ed), which leads to doubled effort of the documentation team and harder sustainability of the code itself. Ideally, all the (rhn-client-tools) strings should be stored at one place together with the translations and GUI and TUI tools should include these strings. See the attached pdf with highlighted differences between TUI and GUI. Version-Release number of selected component (if applicable): rhn-client-tools-2.0.2-5.el7 How reproducible: always Steps to Reproduce: 1. provision RHEL7 guest (with English locale) 2. register the guest against Satellite 5.6 using TUI rhn-client-tools (rhn_register --nox) 3. register the guest against Satellite 5.6 using GUI rhn-client-tools (rhn_register) Actual results: Messages and strings are mostly different and inconsistent, sometimes confusing or confused, containing some typos and grammar mistakes, usually saying almost the same, but in a quite different way, hence we double the translation team effort. Expected results: GUI and TUI messages and strings and the workflow are the same and unified with the same options (in TUI we cannot specify Proxy details, while in GUI we cannot specify the SSL cert path). Additional info: