Hide Forgot
Created attachment 527069 [details] Run facts update with incorrect proxy url produces traceback Description of problem: Run facts update with incorrect proxy url produces traceback Version-Release number of selected component (if applicable): subscription-manager-0.96.12-1.el6 How reproducible: 100%% Steps to Reproduce: 1.Run subscription-manager CLI in terminal (Run via wrong PROXY) $ sudo subscription-manager facts --update --proxy=wrong_PROXY_URL Ex. sudo subscription-manager facts --update --proxy=squid.test.com:3128 Actual results: Run facts update with incorrect proxy url produces traceback Expected results: Should no traceback, it's better to have a warning message to say that the proxy url is incorrect than traceback. Additional info:
is this issue exist in English locale (en_US)?
(In reply to comment #2) > is this issue exist in English locale (en_US)? It not exist in English locale (en_US), I reproduced it in zh_CN locale.
This appears to be working in master now. [root@bkearney ~]# subscription-manager facts --update --proxy=squid.test.com:3128 Error updating system data, see /var/log/rhsm/rhsm.log for more details. [root@bkearney ~]# [root@bkearney ~]# LANG=zh_CN subscription-manager facts --update --proxy=squid.test.com:3128 更新系统数据出错,详情请查看 /var/log/rhsm/rhsm.log。 [root@bkearney ~]#
Moving the bug to verified. RPM used: [root@dhcp201-162 ~]# rpm -qa | grep subscription-manager subscription-manager-0.99.8-1.el6.x86_64 subscription-manager-migration-0.99.8-1.el6.x86_64 subscription-manager-firstboot-0.99.8-1.el6.x86_64 subscription-manager-migration-data-1.12-1.el6.noarch subscription-manager-gnome-0.99.8-1.el6.x86_64 subscription-manager-debuginfo-0.99.8-1.el6.x86_64 [root@dhcp201-162 ~]# LANG=zh_CN.UTF-8 subscription-manager facts --update --proxy=squid.test.com:3128 更新系统数据出错,详情请查看 /var/log/rhsm/rhsm.log。
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-2012-0804.html