Description of problem: Registered SAM with http proxy, after registered it successfully, option "Subscription Asset Manager" was selected ,Registration status display "SAM" and also the field of URL and CA shown SAM configured info . But the field of HTTP Proxy didn't show proxy configured info. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.4-20130109.1.el6 How reproducible: 100% Steps to Reproduce: 1. Install the rhev-hypervisor6-6.4-20130109.1.el6 2. Registered to SAM with proxy. 3. Focus on the page of "Red Hat Network". Actual results: RHN page missed http proxy info after registered SAM with proxy Expected results: RHN page shown http proxy info after registered SAM with proxy Additional info: ----------------
No this issue for registered Public RHN/Satellite with proxy. Only reproduce it for SAM with proxy.
this bug was blocked by Bug 1016557 - RHN Transaction page throw exception when registering to SAM, need waiting for that bug was fixed to check it.
Test version: rhevh-6.5-20131213.0.0.iso ovirt-node-3.0.1-9.el6_5.noarch this bug still was blocked by Bug 1016557 - RHN Transaction page throw exception when registering to SAM, need waiting for that bug was fixed to check it.
Couldn't verify this bug on ovirt-node-3.0.1-16.el6_5.noarch.rpm due to RHN Transaction page throw exception when registering to SAM with proxy , i have report new bug 1051514 to track this issue
Test version: rhev-hypervisor6-6.6-20141107.0.iso ovirt-node-3.1.0-0.25.20141107gitf6dc7b9.el6.noarch Test Steps 1. Install rhev-hypervisor6-6.6-20141107.0.iso 2. Registered to SAM with proxy. (a)registered SAM with http proxy server like "ip:port" (b)registered SAM with http proxy server like "http: //ip:port" After step 2 (a) (b), could see http proxy info in RHN Registration after registered SAM with proxy. so this bug has been fixed in in rhevh 6.6 for RHEV 3.5 bulid version, change the status into "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. https://rhn.redhat.com/errata/RHEA-2015-0160.html