This bug is not easy to reproduce. I managed to reproduce it only after ~300 consequent node failovers. The repro steps can be found here: https://bugs.launchpad.net/fuel/+bug/1458830
The issue is what this commands may does not work as expected:
# rabbitmqctl eval "disconnect_node(list_to_atom(\"rabbit@node-1\"))."; time rabbitmqctl forget_cluster_node rabbit@node-1
and hangs for ever ending up in the situation when none of rabbitmq nodes can't re-join the cluster after faiover because they can't be forgotten and join_cluster reports they are already clustered.
ISO info:
build_id: 2015-05-20_08-41-33
build_number: '441'
but manifests was synced with current master.
This bug is not easy to reproduce. I managed to reproduce it only after ~300 consequent node failovers. The repro steps can be found here: https:/ /bugs.launchpad .net/fuel/ +bug/1458830
The issue is what this commands may does not work as expected: node(list_ to_atom( \"rabbit@ node-1\ "))."; time rabbitmqctl forget_cluster_node rabbit@node-1
# rabbitmqctl eval "disconnect_
and hangs for ever ending up in the situation when none of rabbitmq nodes can't re-join the cluster after faiover because they can't be forgotten and join_cluster reports they are already clustered.
ISO info:
build_id: 2015-05-20_08-41-33
build_number: '441'
but manifests was synced with current master.