Description of problem: Error message "'ascii' codec can't encode characters in position.." . Version-Release number of selected component (if applicable): subscription-manager-0.98.10-1.el5 How reproducible: 100% Steps to Reproduce: 1. Install rhel5.8 snapshot-3 OS build via http://download.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL5.8-Server-20120105.0/5/i386/os/ 2. (Run the command when the system IS registered) $ sudo subscription-manager redeem --email=EMAIL Actual results: Error message "'ascii' codec can't encode characters in position..". Expected results: Should no error message "'ascii' codec can't encode characters in position.." . Additional info:
Created attachment 552324 [details] ascii' codec can't encode characters in position error message
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Testing with versions: python-rhsm-1.0.2-1.git.2.d5c3d05.el5 subscription-manager-1.0.4-1.git.20.0466bff.el5 [root@jmolet-vm0 ~]# subscription-manager clean All local data removed [root@jmolet-vm0 ~]# subscription-manager register --username stage_test_12 Password: The system has been registered with id: d2065fe6-91ea-4419-89d9-fa0783708dcc [root@jmolet-vm0 ~]# subscription-manager redeem --email=test The system is unable to redeem the requested subscription: Not Specified [root@jmolet-vm0 ~]# LANG=zh_TW.UTF8 subscription-manager redeem --email=test The system is unable to redeem the requested subscription: Not Specified [root@jmolet-vm0 ~]# LANG=zh_CN.UTF8 subscription-manager redeem --email=test The system is unable to redeem the requested subscription: Not Specified Cannot reproduce as of above versions using the same steps. We now get the appropriate error message even with other LANG's specified. Marking VERIFIED.
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. http://rhn.redhat.com/errata/RHBA-2013-0033.html