Hide Forgot
Description of problem: [root@jsefler-onprem-62server ~]# subscription-manager environments --username=testuser1 --password=password --org=admin --proxy=foo --proxyuser=man --proxypassword=chu This system does not support environments. ^^^ expected that output to be "Network error, unable to connect to server." since the proxy values I gave were non existent. Version-Release number of selected component (if applicable): [root@jsefler-onprem-62server ~]# rpm -q subscription-manager subscription-manager-0.96.5-1.git.2.d4be8a2.el6.x86_64
Committed b30fa2cd7414e09931724c5839077e6b9c3f8bc5 to python-rhsm Available in python-rhsm 0.98.2+
[root@jmolet-vm4 ~]# subscription-manager environments --username=testuser1 --password=password --org=admin This system does not support environments. [root@jmolet-vm4 ~]# subscription-manager environments --username=testuser1 --password=password --org=admin --proxy=foo Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information. [root@jmolet-vm4 ~]# subscription-manager environments --username=testuser1 --password=password --org=admin --proxy=foo --proxyuser=man --proxypassword=chu Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information. the proxy options are now giving the correct errors, marking VERIFIED python-rhsm-0.98.3-1.git.2.74cd6bb.el5_7 subscription-manager-gnome-0.98.3-1.git.16.14460bc.el5_7 subscription-manager-firstboot-0.98.3-1.git.16.14460bc.el5_7 subscription-manager-0.98.3-1.git.16.14460bc.el5_7
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No description necessary
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-0154.html