Bug 1299214 - Cannot deploy rabbit in an ipv6 environment
Summary: Cannot deploy rabbit in an ipv6 environment
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rabbitmq-server
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: z4
: 7.0 (Kilo)
Assignee: John Eckersberg
QA Contact: Marius Cornea
URL:
Whiteboard:
Depends On:
Blocks: 1299485
TreeView+ depends on / blocked
 
Reported: 2016-01-17 12:37 UTC by Mike Burns
Modified: 2016-02-18 16:10 UTC (History)
7 users (show)

Fixed In Version: rabbitmq-server-3.3.5-15.el7ost
Doc Type: Bug Fix
Doc Text:
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)
Clone Of:
: 1299485 (view as bug list)
Environment:
Last Closed: 2016-02-18 16:10:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0259 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform 7 Bug Fix and Enhancement Advisory 2016-02-18 21:06:38 UTC

Description Mike Burns 2016-01-17 12:37:59 UTC 
Description of problem:
Part of the rabbitmq-server launch is ipv4 only.  See this related issue upstream:

https://github.com/rabbitmq/rabbitmq-server/issues/117

This issue is fixed by https://github.com/rabbitmq/rabbitmq-server/pull/391

Version-Release number of selected component (if applicable):
rabbitmq-server-3.3.5-7.el7ost

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 4 Marius Cornea 2016-01-21 11:50:37 UTC 
[root@overcloud-controller-0 ~]# rabbitmqctl cluster_status
Cluster status of node 'rabbit@overcloud-controller-0' ...
[{nodes,[{disc,['rabbit@overcloud-controller-0',
                'rabbit@overcloud-controller-1',
                'rabbit@overcloud-controller-2']}]},
 {running_nodes,['rabbit@overcloud-controller-2',
                 'rabbit@overcloud-controller-1',
                 'rabbit@overcloud-controller-0']},
 {cluster_name,<<"rabbit@overcloud-controller-0">>},
 {partitions,[]}]
...done.
Comment 7 errata-xmlrpc 2016-02-18 16:10:33 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0259.html
Note You need to log in before you can comment on or make changes to this bug.