Back to bug 1299253

Who When What Removed Added
RHEL Program Management 2016-01-17 21:15:13 UTC Keywords ZStream
Mike Burns 2016-01-18 12:05:06 UTC Priority unspecified urgent
CC mburns
Target Milestone --- z4
Mike Burns 2016-01-18 12:06:02 UTC Status ASSIGNED MODIFIED
Fixed In Version erlang-R16B-03.10min.5.el7ost
errata-xmlrpc 2016-01-18 13:31:24 UTC Status MODIFIED ON_QA
yeylon 2016-01-19 20:24:40 UTC QA Contact yeylon oblaut
Ofer Blaut 2016-01-20 10:25:45 UTC QA Contact oblaut ushkalim
Udi Shkalim 2016-01-24 10:03:20 UTC QA Contact ushkalim ahirshbe
Severity unspecified urgent
Asaf Hirshberg 2016-02-01 09:08:08 UTC Status ON_QA VERIFIED
Don Domingo 2016-02-15 05:13:40 UTC Flags needinfo?(jeckersb)
John Eckersberg 2016-02-16 19:26:21 UTC Doc Text Cause: The Erlang port mapper daemon (epmd) only binds and listens for connections on IPv4 addresses.

Consequence: Attempting to form an Erlang cluster in an IPv6-only environment fails.

Fix: Update epmd to listen on IPv6 addresses, and update clients to register and query epmd over IPv6.

Result: Erlang clustering works in an IPv6-only environment.
Flags needinfo?(jeckersb)
Don Domingo 2016-02-16 23:49:02 UTC CC ddomingo
Doc Text Cause: The Erlang port mapper daemon (epmd) only binds and listens for connections on IPv4 addresses.

Consequence: Attempting to form an Erlang cluster in an IPv6-only environment fails.

Fix: Update epmd to listen on IPv6 addresses, and update clients to register and query epmd over IPv6.

Result: Erlang clustering works in an IPv6-only environment.
The Erlang port mapper daemon (epmd) can now listen on IPv6 addresses. In addition, clients can now register and query epmd over IPv6. This, in turn, now allows Erlang clustering to work in an IPv6-only environment. Previously, epmd could only bind and listen on IPv4 addresses, thereby preventing the formation of Erlang clusters in IPv6-only environments.c
errata-xmlrpc 2016-02-18 09:39:19 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-02-18 16:10:44 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-02-18 11:10:44 UTC

Back to bug 1299253