Bug 1386611

Summary: OSP10 - rabbitmq cluster_status shows nodedown alerts, list_queues / list_connections hang
Product: Red Hat OpenStack Reporter: Michele Baldessari <michele>
Component: puppet-tripleoAssignee: Michele Baldessari <michele>
Status: CLOSED ERRATA QA Contact: Asaf Hirshberg <ahirshbe>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 10.0 (Newton)CC: apevec, bschmaus, cpaquin, dmacpher, fdinitto, jeckersb, jjoyce, jschluet, lhh, mburns, michele, pbandark, plemenko, rhel-osp-director-maint, slinaber, srevivo, tvignaud, ushkalim, vcojot
Target Milestone: rcKeywords: Triaged
Target Release: 10.0 (Newton)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: puppet-tripleo-5.3.0-3.el7ost Doc Type: Bug Fix
Doc Text:
rabbitmqctl failed to function in an IPv6 environment due to a missing parameter. This fix modifies the RabbitMQ Puppet configuration and adds the missing parameter to /etc/rabbitmq/rabbitmq-env.conf. Now rabbitmqctl does not fail in IPv6 environments
 Story Points: ---
Clone Of: 1384571 Environment:
Last Closed: 2016-12-14 16:22:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Asaf Hirshberg 2016-11-06 09:02:12 UTC 
Verified Using puppet-tripleo-5.3.0-4.el7ost.noarch.
Also verified that reboot doesn't affect it.

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-1',
                 'rabbit@overcloud-controller-2',
                 'rabbit@overcloud-controller-0']},
 {cluster_name,<<"rabbit">>},
 {partitions,[]},
 {alarms,[{'rabbit@overcloud-controller-1',[]},
          {'rabbit@overcloud-controller-2',[]},
          {'rabbit@overcloud-controller-0',[]}]}]
[heat-admin@overcloud-controller-0 ~]$ exit

[heat-admin@overcloud-controller-1 ~]$ sudo rabbitmqctl cluster_status
Cluster status of node 'rabbit@overcloud-controller-1' ...
[{nodes,[{disc,['rabbit@overcloud-controller-0',
                'rabbit@overcloud-controller-1',
                'rabbit@overcloud-controller-2']}]},
 {running_nodes,['rabbit@overcloud-controller-0',
                 'rabbit@overcloud-controller-2',
                 'rabbit@overcloud-controller-1']},
 {cluster_name,<<"rabbit">>},
 {partitions,[]},
 {alarms,[{'rabbit@overcloud-controller-0',[]},
          {'rabbit@overcloud-controller-2',[]},
          {'rabbit@overcloud-controller-1',[]}]}]
[heat-admin@overcloud-controller-1 ~]$ exit

[heat-admin@overcloud-controller-2 ~]$ sudo rabbitmqctl cluster_status
Cluster status of node 'rabbit@overcloud-controller-2' ...
[{nodes,[{disc,['rabbit@overcloud-controller-0',
                'rabbit@overcloud-controller-1',
                'rabbit@overcloud-controller-2']}]},
 {running_nodes,['rabbit@overcloud-controller-1',
                 'rabbit@overcloud-controller-0',
                 'rabbit@overcloud-controller-2']},
 {cluster_name,<<"rabbit">>},
 {partitions,[]},
 {alarms,[{'rabbit@overcloud-controller-1',[]},
          {'rabbit@overcloud-controller-0',[]},
          {'rabbit@overcloud-controller-2',[]}]}]
[heat-admin@overcloud-controller-2 ~]$
Comment 4 errata-xmlrpc 2016-12-14 16:22:15 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/RHEA-2016-2948.html