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 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:
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 ~]#
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
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: