Comment 6 for bug 1539586

Tatyana, I agree with Alexey, there is clear indication in sys_test.log
https://product-ci.infra.mirantis.net/view/8.0_swarm/job/8.0.system_test.ubuntu.ha_neutron_destructive/123/

that cluster was up again in 01:51:01:

2016-01-29 01:51:01,569 - DEBUG __init__.py:59 -- Done: run_on_remote_get_results with result: {'stdout_len': 7, 'stderr_len': 0, 'stdout': ["Cluster status of node 'rabbit@messaging-node-1' ...\n", "[{nodes,[{disc,['rabbit@messaging-node-1','rabbit@messaging-node-2',\n", " 'rabbit@messaging-node-5']}]},\n", " {running_nodes,['rabbit@messaging-node-2','rabbit@messaging-node-5',\n", " 'rabbit@messaging-node-1']},\n", ' {cluster_name,<<"<email address hidden>">>},\n', ' {partitions,[]}]\n'], 'exit_code': 0, 'stderr_str': '', 'stderr': [], 'stdout_str': 'Cluster status of node \'rabbit@messaging-node-1\' ...\n[{nodes,[{disc,[\'rabbit@messaging-node-1\',\'rabbit@messaging-node-2\',\n \'rabbit@messaging-node-5\']}]},\n {running_nodes,[\'rabbit@messaging-node-2\',\'rabbit@messaging-node-5\',\n \'rabbit@messaging-node-1\']},\n {cluster_name,<<"<email address hidden>">>},\n {partitions,[]}]\n'}

Also, first time cluster_status check was performed just 3 minutes earlier - at 01:48:34. I.e. RabbitMQ reassembled in 3 minutes.

Could you please clarify what exaclty made the test failed?