Looks like the test case described in the bug was not performed well: http://pastebin.com/jZ5UM6qb (from logs in #1)
As you can see, the full reboot AND cluster reassemble verify period was less than 5 minutes, and logs snapshot was taken too early - before the cluster managed to reassemble.
The correct check should:
1) measure time-to-reassemble from the moment of time then rebooting has been finished, instead of then it was initiated.
2) measure time-to-reassemble for any given node between the moments then corosync started and the time stamp of the nearest 'rabbit app is running and is member of healthy cluster' event.
Looks like the test case described in the bug was not performed well: http:// pastebin. com/jZ5UM6qb (from logs in #1)
As you can see, the full reboot AND cluster reassemble verify period was less than 5 minutes, and logs snapshot was taken too early - before the cluster managed to reassemble.
The correct check should:
1) measure time-to-reassemble from the moment of time then rebooting has been finished, instead of then it was initiated.
2) measure time-to-reassemble for any given node between the moments then corosync started and the time stamp of the nearest 'rabbit app is running and is member of healthy cluster' event.