Bug 1305647

Summary:	OSAD is unable to connect to spacewalk via spacewalk proxy
Product:	[Community] Spacewalk	Reporter:	Bartek Rekke <bojleros>
Component:	Clients	Assignee:	Michael Mráka <mmraka>
Status:	CLOSED EOL	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.4	CC:	garysonn
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-21 13:12:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Bartek Rekke 2016-02-08 19:57:41 UTC

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:

Comment 1 Ivan 2019-09-11 17:41:57 UTC

Hi,
Did you find solution?

Comment 2 Michael Mráka 2019-10-21 13:12:09 UTC

Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.