+++ This bug was initially created as a clone of Bug #567789 +++ Description of problem: osad cannot connect to Spacewalk via a Squid proxy. Version-Release number of selected component (if applicable): osad-5.11.27-1 How reproducible: Always Steps to Reproduce: 1. Spacewalk 2.1, registered client(s), Squid proxy in between 2. Configure your client (/etc/sysconfig/rhn/up2date) to use http proxy, optionally with authentication 3. Install & start osad on your client Actual results: osad will attempt to connecto to the parent Spacewalk rather than the configured Squid proxy. Expected results: osad will honor & use http proxy settings. Additional info: N/A
spacewalk.git master: 401b64c6ccc1a09fcda05280fbf745c838cbc32c
Spacewalk 2.2 has been released: https://fedorahosted.org/spacewalk/wiki/ReleaseNotes22
This fix has a problem, if using an unauthenticated proxy and having set enableProxyAuth=0 in /etc/sysconfig/rhn/up2date, you will get this error: Error caught: 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 306, in _get_jabber_client if cf['enable_proxy_auth']: KeyError: 'enable_proxy_auth' Committing to Spacewalk master: 50b9546ad2854c27fab998a1734fcdc71eaf9b82
Moving bugs to ON_QA as we move to release Spacewalk 2.3
Spacewalk 2.3 has been released. See https://fedorahosted.org/spacewalk/wiki/ReleaseNotes23