Bug 715299

Summary:	RHN Satellite's standard jabberd setup is not IPv6 ready
Product:	Red Hat Satellite 5	Reporter:	Milan Zázrivec <mzazrivec>
Component:	Server	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Studeník <pstudeni>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	541	CC:	cperry, mkorbel, pstudeni
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-setup-jabberd-1.6.5-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-09-21 09:17:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	819030

Description Milan Zázrivec 2011-06-22 13:49:34 UTC

Description of problem:
jabberd services (c2s, s2s, router, sm) so as they are configured by
spacewalk-setup-jabberd are not ready to be deployed in an IPv6 only
environment.

In particular:

c2s.xml:
* /c2s/local/ip needs to be modified for IPv6

router.xml:
* /router/local/ip needs to be modified for IPv6

s2s.xml:
* /s2s/local/ip needs to be modified for IPv6
* /s2s/lookup/resolve-ipv6 needs to be enabled

Version-Release number of selected component (if applicable):
spacewalk-setup-jabberd-1.2.1-1

How reproducible:
Always

Steps to Reproduce:
1. Install Satellite 5.4.1 in an IPv6 only environment
2. Check whether jabberd services (c2s, router, s2s) are bound & listening
   to an IPv6 address
  
Actual results:
jabberd services do not work in an IPv6 only environment

Expected results:
jabberd services do work in an IPv6 only environment

Additional info:
This needs to be resolved for a successful Satellite IPv6 installation.

Comment 1 Milan Zázrivec 2011-10-07 13:59:07 UTC

spacewalk.git master: 134906057370c0e3620a07568d4e5016c5957844

Comment 2 Milan Zázrivec 2011-10-19 11:11:12 UTC

spacewalk.git master: 2c1cd81b56b80fc397ffe0aafa9e742f7e210db9

Comment 6 Clifford Perry 2012-09-21 09:17:08 UTC

This issue is resolved with the release of RHN Satellite 5.5. 

As of September 20th 2012, RHN Satellite 5.5 has been generally available. 

Release Notes and other 5.5 documentation can be found here:

 https://access.redhat.com/knowledge/docs/Red_Hat_Network_Satellite/

The associated Errata for the 5.5 release are:

5.5 Satellite GA Errata
 - http://rhn.redhat.com/errata/RHEA-2012-1296.html

5.5 Upgrade Errata
 - http://rhn.redhat.com/errata/RHEA-2012-1298.html

5.5 RHN Proxy GA Errata
 - http://rhn.redhat.com/errata/RHEA-2012-1297.html

5.5 RHN Tools GA Errata
 - http://rhn.redhat.com/errata/RHEA-2012-1299.html

Regards,
Clifford
- Engineering Manager, Satellite