Created attachment 1111558 [details] Sosreport from SAM 1.4.3 server Description of problem: SAM manifest refresh from server does not use http proxy settings as expected. Version-Release number of selected component (if applicable): SAM 1.4.3 RHEL 6.7 x86_64 How reproducible: Always Steps to Reproduce: 1. Attempt manifest refresh from the SAM webui according to: https://access.redhat.com/documentation/en-US/Red_Hat_Subscription_Management/1/html-single/Using_Subscription_Asset_Manager/index.html#sam-manifest-org Actual results: SAM server appears to use port 443 and goes directly to RHN rather than use the http set in various locations: [root@SAM ~]# tcpdump -fnn -i eth0 not port 22 and not port 514 and not port 8649 and not port 123 and not arp and not rarp and not port 389 and not host 10.11.23.204 and not host 192.168.129.140 and not port 137 and not port 138 and not port 53 and not icmp and not port 88 and not host 192.168.130.45 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 16:27:06.967156 IP 192.168.130.66.46968 > 209.132.183.107.443: Flags [S], seq 3659201829, win 14600, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0 16:27:06.967315 IP 209.132.183.107.443 > 192.168.130.66.46968: Flags [R.], seq 0, ack 3659201830, win 14600, length 0 ^C 2 packets captured 2 packets received by filter 0 packets dropped by kernel [root@SAM~]# rhsm.conf: ~~~ # an http proxy server to use proxy_hostname = http://<PROXY.FQDN> # port for http proxy server proxy_port = 3128 ~~~ thumbslug.conf ~~~ cdn.proxy = true cdn.proxy.host = http://<PROXY.FQDN> cdn.proxy.port = 3128 ~~~ katello-configure.conf ~~~ # proxy_url proxy_url = http://<PROXY.FQDN> # proxy_port proxy_port = 3128 ~~~ Expected results: SAM will route through the http por Additional info: See attached soreports and katello-debugs
Created attachment 1111559 [details] SAM Katello-debug
Same problem here. RHEL 6.5
We are closing this bug as a WONTFIX as there are currently no planned updates or future releases for SAM 1.X This may change in the future if we decide to revive the SAM offering with a rebase off the current Satellite 6.X technology stack but there is nothing planned at this time.