[Spacewalk-list] Spacewalk client - yum - proxy behavior

[Jan Arild Lindstrøm]

Hi,

installed CentOS the normal way, updated everything, rebooted
and then installed the Spacewalk client.

1)

lintest3-virt(root) ~ 32# egrep 'proxy=|enableProxy=|httpProxy=' /etc/yum.conf /etc/sysconfig/rhn/up2date 
/etc/yum.conf:proxy=http://proxy-z2.mydomain.no:8080
/etc/sysconfig/rhn/up2date:enableProxy=1
/etc/sysconfig/rhn/up2date:httpProxy=proxy-z2.mydomain.no:8080

2)

lintest3-virt(root) ~ 33# spacewalk-channel --list
centos6-x86_64
centos6-x86_64-addons
centos6-x86_64-contrib
centos6-x86_64-extras
centos6-x86_64-fasttrack
centos6-x86_64-updates
epel6-centos6-x86_64
spacewalk16-client-centos6-x86_64

That is, "spacewalk-channel --list" uses the proxy all the way. It does not
try to connect to the Spacewalk server directly.

3)

lintest3-virt(root) ~ 34# yum update
Loaded plugins: refresh-packagekit, rhnplugin, security
Loading mirror speeds from cached hostfile
Error: Cannot retrieve repository metadata (repomd.xml) for repository: centos6-x86_64. Please verify its path and try again

( - "yum update" starts here - )
14:20:33.362368 IP 10.10.0.62.51822 > 10.10.30.183.8080: tcp 0
14:20:33.375652 IP 10.10.30.183.8080 > 10.10.0.62.51822: tcp 0
14:20:33.375852 IP 10.10.0.62.51822 > 10.10.30.183.8080: tcp 0
14:20:33.377344 IP 10.10.0.62.51822 > 10.10.30.183.8080: tcp 627
14:20:33.377522 IP 10.10.0.62.51822 > 10.10.30.183.8080: tcp 1380
14:20:33.378321 IP 10.10.30.183.8080 > 10.10.0.62.51822: tcp 0
--cut--
14:20:33.402821 IP 10.10.0.62.51822 > 10.10.30.183.8080: tcp 0
14:20:33.402825 IP 10.10.30.183.8080 > 10.10.0.62.51822: tcp 467
14:20:33.402829 IP 10.10.0.62.51822 > 10.10.30.183.8080: tcp 0
14:20:33.402846 IP 10.10.30.183.8080 > 10.10.0.62.51822: tcp 0
14:20:33.406011 IP 10.10.0.62.51822 > 10.10.30.183.8080: tcp 0
14:20:33.406976 IP 10.10.30.183.8080 > 10.10.0.62.51822: tcp 0
14:20:33.460341 IP 10.10.0.62.50796 > 10.10.0.60.80: tcp 0
14:20:36.460258 IP 10.10.0.62.50796 > 10.10.0.60.80: tcp 0
14:20:42.460278 IP 10.10.0.62.50796 > 10.10.0.60.80: tcp 0
--cut--

Proxy = 10.10.30.183
Spacewalk server = 10.10.0.62

That is "yum update" starts using the proxy, but after some packets start using
the Spacewalk server directly without going through the proxy, and hence it 
fails.

4)

lintest3-virt(root) ~ 105# yum repolist
Loaded plugins: refresh-packagekit, rhnplugin, security
repo id                                       repo name                                              status
centos6-x86_64                                CentOS 6 (x86_64)                                      0
centos6-x86_64-addons                         CentOS 6 Addons (x86_64)                               0
centos6-x86_64-contrib                        CentOS 6 Contrib (x86_64)                              0
centos6-x86_64-extras                         CentOS 6 Extras (x86_64)                               0
centos6-x86_64-fasttrack                      CentOS 6 FastTrack (x86_64)                            0
centos6-x86_64-updates                        CentOS 6 Updates (x86_64)                              0
epel6-centos6-x86_64                          EPEL 6 for CentOS 6 (x86_64)                           0
spacewalk16-client-centos6-x86_64             Spacewalk Client 1.6 for CentOS 6 (x86_64)             0
repolist: 0

( - "yum repolist" starts here - )
14:56:17.023945 IP 10.10.0.62.51838 > 10.10.30.183.8080: tcp 0
14:56:17.035872 IP 10.10.30.183.8080 > 10.10.0.62.51838: tcp 0
14:56:17.035922 IP 10.10.0.62.51838 > 10.10.30.183.8080: tcp 0
14:56:17.037405 IP 10.10.0.62.51838 > 10.10.30.183.8080: tcp 627
14:56:17.037487 IP 10.10.0.62.51838 > 10.10.30.183.8080: tcp 1380
14:56:17.038154 IP 10.10.30.183.8080 > 10.10.0.62.51838: tcp 0
--cut--
14:56:17.296432 IP 10.10.0.62.51838 > 10.10.30.183.8080: tcp 0
14:56:17.297259 IP 10.10.30.183.8080 > 10.10.0.62.51838: tcp 0
14:56:17.352620 IP 10.10.0.62.50812 > 10.10.0.60.80: tcp 0
14:56:20.351199 IP 10.10.0.62.50812 > 10.10.0.60.80: tcp 0
14:56:26.351144 IP 10.10.0.62.50812 > 10.10.0.60.80: tcp 0
--cut--

Proxy = 10.10.30.183
Spacewalk server = 10.10.0.62

That is "yum repolist" starts using the proxy, but after some packets start using
the Spacewalk server directly without going through the proxy. It finds the channels,
but fail to find any packages in the channels.


Yum only works all the way if I do the following:
  lintest3-virt(root) ~ 49# http_proxy=http://proxy-z2.mydomain.no:8080
  lintest3-virt(root) ~ 50# export http_proxy

Why do one need to use http_proxy in the environment? Should not yum and the 
Spacewalk client stuff read all the proxy settings it needs from /etc/yum.conf 
and /etc/sysconfig/rhn/up2date?

If I remove Spacewalk client and enable the "normal" repos again, yum uses the 
proxy all the way. It seems to be something in the Spacewalk client that does 
not care about proxy settings found in /etc/yum.conf and /etc/sysconfig/rhn/up2date. 

Anyone got this to work without http_proxy in the environment after intalling
Spacewalk client?

---
Regards
Jan Arild