Created attachment 506027 [details] Patch addressing the issue Description of problem: jabberpy library (and by extension osad / osa-dispatcher) are not IPv6 ready. The library simply assumes all connections to jabber server are plan IPv4. Version-Release number of selected component (if applicable): jabberpy-0.5-0.20 How reproducible: Always Steps to Reproduce: 1. Install Satellite 5.4.1 in an IPv6 only environment 2. Make sure jabberd services are listening on IPv6 addresses (but #715299) 3. Check osa-dispatcher startup. Actual results: osa-dispatcher won't start, following error is present in osa-dispatcher.log: Traceback (most recent call last): File "/usr/share/rhn/osad/jabber_lib.py", line 254, in setup_connection c = self._get_jabber_client(js) File "/usr/share/rhn/osad/jabber_lib.py", line 311, in _get_jabber_client c.connect() File "/usr/share/rhn/osad/jabber_lib.py", line 577, in connect jabber.Client.connect(self) File "/usr/lib/python2.6/site-packages/jabber/xmlstream.py", line 464, in connect else: self._sock.connect((self._hostIP, self._port)) File "<string>", line 1, in connect gaierror: [Errno -2] Name or service not known Expected results: osa-dispatcher starts all right. Additional info: Required for a successful IPv6 Satellite deployment.
Problem has also been addressed in EPEL (being used in Spacewalk) packages: http://koji.fedoraproject.org/koji/buildinfo?buildID=265023 http://koji.fedoraproject.org/koji/buildinfo?buildID=265022
thirdparty.git SATELLITE-5.4: 46196d64086409d7d285a5b3e6641c0f21f11a5a
*** Bug 790797 has been marked as a duplicate of this bug. ***
When building the packages, please also add fix for bug 740351.