RabbitMQ cluster settings wrong at primary-controller

Bug #1315681 reported by Sergey Vasilenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Library (Deprecated)

Bug Description

Centos, HA, 3 controllers

After fresh deploy we have:
18:01:40 (xenolog@primus) ~
$ ssh 10.22.0.4
Warning: Permanently added '10.22.0.4' (RSA) to the list of known hosts.
Last login: Mon Apr 28 13:24:20 2014 from 10.22.0.1
[root@node-1 ~]# rabbitmqctl cluster_status
Cluster status of node 'rabbit@node-1' ...
[{nodes,[{disc,['rabbit@node-1']}]},
 {running_nodes,['rabbit@node-1']},
 {partitions,[]}]
...done.

We have no node-2,node-3 in the nodes-list.

Anybody else, please try to confirm this!!!

Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

{"build_id": "2014-05-02_19-39-15", "mirantis": "yes", "build_number": "32", "ostf_sha": "134765fcb5a07dce0cd1bb399b2290c988c3c63b", "nailgun_sha": "621dbc810c52d5150ad0cc1edb8e8be379985097", "production": "docker", "api": "1.0", "fuelmain_sha": "95c35c199c2efc03fb105d090c5a42525430b7b3", "astute_sha": "3cffebde1e5452f5dbf8f744c6525fc36c7afbf3", "release": "5.0", "fuellib_sha": "984becba67d6fb911988ff38a9ddd1f47144fbdc"}

not confirmed with custom ISO identical to master ISO build #177

[root@node-1 ~]# cat /etc/rabbitmq/rabbitmq.config
% This file managed by Puppet 3.4.2
% Template Path: rabbitmq/templates/rabbitmq.config
[
  {kernel, [
    {inet_dist_listen_min, 41055},
    {inet_dist_listen_max, 41055},
    {inet_default_connect_options, [{nodelay,true}]}
  ]}
  ,{rabbit, [
    {log_levels, [connection,debug,info,error]},
    {cluster_nodes, ['rabbit@node-3', 'rabbit@node-2', 'rabbit@node-1']}
  ]}
].
% EOF
[root@node-1 ~]# rabbitmqctl cluster_status
Cluster status of node 'rabbit@node-1' ...
[{nodes,[{disc,['rabbit@node-1','rabbit@node-2','rabbit@node-3']}]},
 {running_nodes,['rabbit@node-3','rabbit@node-2','rabbit@node-1']},
 {partitions,[]}]
...done.

Changed in fuel:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.