Bug 1305647 - OSAD is unable to connect to spacewalk via spacewalk proxy
OSAD is unable to connect to spacewalk via spacewalk proxy
Status: NEW
Product: Spacewalk
Classification: Community
Component: Clients (Show other bugs)
2.4
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Tomáš Kašpárek
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-08 14:57 EST by Bartek Rekke
Modified: 2016-02-08 14:57 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bartek Rekke 2016-02-08 14:57:41 EST
Hi,

I have few centos7 and few centos6 installed in remote location. Both was registered in a same way:

osad-5.11.62-1.el7.noarch

rhnreg_ks --serverUrl=http://spacewalk/XMLRPC --activationkey=1-key --force --proxy=spaceproxy:8080

There are following packages installed:
osad-5.11.62-1.el7.noarch (on Centos7)
osad-5.11.62-1.el6.noarch (on Centos6)

I have checked up2date.conf on all hosts and they are all having exactly the same:

enableProxy=1
serverURL=https://spacewalk/XMLRPC
sslCACert=proper_same_key
httpProxy=spaceproxy:8080

Hosts gets registered correctly but for Centos6 i get following error on osad restart:

Shutting down osad:                                        [  OK  ]
Starting osad: 2016-02-08 20:47:13 rhn_log.log_error: 0 Error caught:
Error caught:
2016-02-08 20:47:13 rhn_log.log_error: 0 Traceback (most recent call last):
  File "/usr/share/rhn/osad/jabber_lib.py", line 119, in main
    c = self.setup_connection(no_fork=no_fork)
  File "/usr/share/rhn/osad/jabber_lib.py", line 253, in setup_connection
    c = self._get_jabber_client(js)
  File "/usr/share/rhn/osad/jabber_lib.py", line 321, in _get_jabber_client
    c.connect()
  File "/usr/share/rhn/osad/jabber_lib.py", line 590, in connect
    jabber.Client.connect(self)
  File "/usr/lib/python2.6/site-packages/jabber/xmlstream.py", line 528, in connect
    except: raise error('Invalid proxy reply')
error: Invalid proxy reply

Traceback (most recent call last):
  File "/usr/share/rhn/osad/jabber_lib.py", line 119, in main
    c = self.setup_connection(no_fork=no_fork)
  File "/usr/share/rhn/osad/jabber_lib.py", line 253, in setup_connection
    c = self._get_jabber_client(js)
  File "/usr/share/rhn/osad/jabber_lib.py", line 321, in _get_jabber_client
    c.connect()
  File "/usr/share/rhn/osad/jabber_lib.py", line 590, in connect
    jabber.Client.connect(self)
  File "/usr/lib/python2.6/site-packages/jabber/xmlstream.py", line 528, in connect
    except: raise error('Invalid proxy reply')
error: Invalid proxy reply

                                                           [  OK  ]

This problem disappear just after changing enableProxy=0 inside up2date on every Centos6 host. I have also noted that on enableProxy=0 inside osad.conf on Centos6 does not help. It seems like I am facing two problems:

1. osad on Centos6 have problems with connecting to spacewalk via spacewalk-proxy.
2. Parameters defined in osad.conf does not take precedence over one defined inside up2date.



How reproducible:

On every installation of Centos6.

Steps to Reproduce:

Just follow manual, install spacewalk, spacewalk-proxy, all necessary packages (including osad) on Centos6 and then join host to the spacewalk. Try to restart osad. 

Actual results:
Yum sessions are being forwarded via proxy but I am unable to run remote command and update packages when proxy is configured. I have to turn off proxy in up2date file but then I will lost my local cache.

Expected results:

Osad worrking with proxy and without proxy as in Centos7. Parameters in osad.conf are being obeyed.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.