Back to bug 1299214

Who When What Removed Added
Mike Burns 2016-01-17 12:39:45 UTC Status NEW ON_DEV
CC mburns
RHEL Program Management 2016-01-17 12:55:03 UTC Keywords ZStream
Javier Peña 2016-01-18 12:21:22 UTC CC jpena
Mike Burns 2016-01-18 13:37:54 UTC Blocks 1299485
Mike Burns 2016-01-18 13:39:09 UTC Status ON_DEV MODIFIED
Fixed In Version rabbitmq-server-3.3.5-15.el7ost
Mike Burns 2016-01-18 13:42:23 UTC Priority unspecified urgent
errata-xmlrpc 2016-01-18 17:11:13 UTC Status MODIFIED ON_QA
yeylon 2016-01-19 20:25:17 UTC QA Contact yeylon mcornea
Marius Cornea 2016-01-21 11:50:37 UTC Status ON_QA VERIFIED
Don Domingo 2016-02-15 05:13:34 UTC Flags needinfo?(jeckersb)
John Eckersberg 2016-02-16 16:34:45 UTC Doc Text Cause: RabbitMQ assumes during startup that IPv4 is to be used when checking ability to bind to distribution port.

Consequence: In IPv6-only environments, distribution port bind check fails and thus RabbitMQ fails to start.

Fix: Port check first tries IPv4, and if that fails will try IPv6.

Result: RabbitMQ can start successfully in an IPv6-only environment.
Flags needinfo?(jeckersb)
Don Domingo 2016-02-17 00:08:16 UTC CC ddomingo
Doc Text Cause: RabbitMQ assumes during startup that IPv4 is to be used when checking ability to bind to distribution port.

Consequence: In IPv6-only environments, distribution port bind check fails and thus RabbitMQ fails to start.

Fix: Port check first tries IPv4, and if that fails will try IPv6.

Result: RabbitMQ can start successfully in an IPv6-only environment.
When checking for a distribution port, RabbitMQ will now check for IPv6 addresses if no IPv4 addresses are available. This ensures that RabbitMQ can start successfully in an IPv6-only environment. Previously, RabbitMQ only checked for IPv4 addresses; if none were found (as in an IPv6-only environment), the RabbitMQ port check (and by extension, startup) failed. (BZ#1299214)
errata-xmlrpc 2016-02-18 09:39:12 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-02-18 16:10:33 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-02-18 11:10:33 UTC

Back to bug 1299214