Description of problem: qdrouterd should listen to ipv6 Version-Release number of selected component (if applicable): Satellite 6.1 GA Snap 3 Compose 2 How reproducible: Always Steps to Reproduce: 1. In satellite:1 qdrouterd is listening only in tcp and not in tcp6. see below # netstat -tlpn | grep qdrouterd tcp 0 0 0.0.0.0:5646 0.0.0.0:* LISTEN 27324/qdrouterd tcp 0 0 0.0.0.0:5647 0.0.0.0:* LISTEN 27324/qdrouterd Actual results: Sometimes content-hosts are trying to connect to qdrouterd using ipv6 and fails Expected results: qdrouterd in satellite should listen to ipv6 as well. Additional info:
related qdrouterd issue https://issues.apache.org/jira/browse/DISPATCH-190
Created redmine issue http://projects.theforeman.org/issues/12386 from this bug
Upstream bug component is WebUI
If the "listener" in /etc/qpid-dispatch/qdrouterd.conf is changed from listener { addr: 0.0.0.0 port: 5647 sasl-mechanisms: ANONYMOUS ssl-profile: server } to listener { addr: :: port: 5647 sasl-mechanisms: ANONYMOUS ssl-profile: server } It seems to me that it will open a IPv6 dualsocket? Answering both IPv6 and IPv4 qdrouterd 14385 qdrouterd 8u IPv6 9958453 0t0 TCP [2001:470:28:82e:5054:ff:fe70:753f]:5647->[2001:470:28:82e:5054:ff:fe7b:b0e1]:53172 (ESTABLISHED) qdrouterd 14385 qdrouterd 9u IPv6 9957171 0t0 TCP 192.168.0.5:5647->192.168.0.5:45640 (ESTABLISHED)
Moving 6.2 bugs out to sat-backlog.
Workaround in comment#5 is nice but won't survive next installer run as installer resets addr: from "::" to "0.0.0.0"
We can easily change https://github.com/Katello/puppet-foreman_proxy_content/blob/2cfba42ae5297a4a7a1b58804213ec5dc867c184/manifests/params.pp#L23 and https://github.com/Katello/puppet-foreman_proxy_content/blob/2cfba42ae5297a4a7a1b58804213ec5dc867c184/manifests/params.pp#L27 to "::". It might be needed to also create a migration in the installer to change it in answer files. My question is if listening to "::" rather than "0.0.0.0" will always work or if we need to check the ipaddress6 fact to check if an IPv6 address is present.
Upstream bug assigned to ekohlvan
Ewoud, I answer your question by another question, how is it already done for qpidd ? (5671/tcp and 5672/tcp) Grepping listening ports shows us that qpidd is already IPv6 ready while qdrouterd is not, only IPv4 (5646/tcp and 5647/tcp) # netstat -plnt | grep /q.*d tcp 0 0 0.0.0.0:5646 0.0.0.0:* LISTEN 13427/qdrouterd tcp 0 0 0.0.0.0:5647 0.0.0.0:* LISTEN 13427/qdrouterd tcp 0 0 127.0.0.1:5671 0.0.0.0:* LISTEN 13407/qpidd tcp 0 0 127.0.0.1:5672 0.0.0.0:* LISTEN 13407/qpidd tcp6 0 0 ::1:5671 :::* LISTEN 13407/qpidd tcp6 0 0 ::1:5672 :::* LISTEN 13407/qpidd
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.