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.
Description of problem:
Similar to bug 1149098, the word "unentitle" is not recognized by dictionary.com.
It is used in the following two msgids...
[root@jsefler-os7 ~]# msgunfmt --no-wrap /usr/share/locale/fr/LC_MESSAGES/rhsm.mo | grep "unentitle" -B1
msgid "Could not unentitle system on legacy server. "
--
msgid "state to leave system in on legacy server (not available in hosted environments; default is 'unentitle')"
These two strings are used in the context of the sat5to6 tool which employs rhn-channel tooling whose help message reports options:
-c CHANNEL, --channel=CHANNEL
name of channel you want to (un)subscribe
-a, --add subscribe to channel
-r, --remove unsubscribe from channel
Therefore I suggest re-wording the subscription-manager msgids to...
msgid "Could not remove channels from system on legacy server. "
msgid "state to leave system in on legacy server (not available in hosted environments; default is 'unsubscribed')"
Additional note:
If these string changes are implemented, it appears to also affect the --registration-state and valid_states = ["keep", "unentitle", "purge"] in migrate.py
Version-Release number of selected component (if applicable):
[root@jsefler-os7 ~]# rpm -q subscription-manager
subscription-manager-1.13.19-1.el7.x86_64
commit 599f217a4cf06248720fa0a30bd08b0b4ecc0f18
Author: Chris Rog <crog>
Date: Wed Apr 8 10:33:03 2015 -0400
1189880: Removed the non-word "unentitle" from error messages
- Removed the two instances of "unentitle" from error messages output
when revoking a system's entitlement fails.
- The term still exists as a system state and option.
[root@jsefler-6 ~]# rpm -q --whatprovides /usr/share/locale/fr/LC_MESSAGES/rhsm.mo
subscription-manager-1.16.8-1.el6.x86_64
The new msgids have been changed to the following...
[root@jsefler-6 ~]# msgunfmt --no-wrap /usr/share/locale/fr/LC_MESSAGES/rhsm.mo | grep "on legacy server"
msgid "Could not remove system entitlement on legacy server. "
msgid "state to leave system in on legacy server (default is '%s')"
Notice that "unentitle system" has been changed to "remove system entitlement" in the first msgid
Notice that string substitution is now being used in the second msgid where "unentitle" will remain as a system state as indicated in comment 1
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-0797.html