Project

General

Profile

Bug #28672

qpid's wait-for-port ExecStartPost checks 127.0.0.1 which breaks on IPv6

Added by Ewoud Kohl van Wijngaarden 7 months ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:

Description

QPid binds to whatever connectivity is available on an external interface, ignoring lo. This means it's configured to bind to localhost it only binds to ::1 when eth0 is the only interface and IPv6 only. The wait-for-port override connects to 127.0.0.1:$ssl_port and fails.

Since netcat can connect to DNS, the solution is to connect to localhost instead of an IP.

A Bugzilla that describes a similar problem https://bugzilla.redhat.com/show_bug.cgi?id=1055660


Related issues

Related to Foreman - Tracker #28683: IPv6 only supportNew

Associated revisions

Revision 2d92c9a5 (diff)
Added by Ewoud Kohl van Wijngaarden 7 months ago

Fixes #28672 - Check if qpid is up using localhost

Given a machine that has 127.0.0.1 / ::1 on lo and eth0 has 2001:db::1,
in other works, no IPv4 connectivity, then qpid qpid binds only on IPv6,
even when a host needs to listen on localhost. Since netcat can connect
to either, it is a safe check.

History

#1 Updated by The Foreman Bot 7 months ago

  • Assignee set to Ewoud Kohl van Wijngaarden
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-qpid/pull/128 added

#2 Updated by The Foreman Bot 7 months ago

  • Fixed in Releases 2.0.0 added

#3 Updated by Ewoud Kohl van Wijngaarden 7 months ago

  • Status changed from Ready For Testing to Closed

#4 Updated by Ewoud Kohl van Wijngaarden 7 months ago

Also available in: Atom PDF