Comment 14 for bug 1348548

I verified the 'stop' policy, and I can confirm what w/o fencing enabled, cluster will remain in broken/partitioning state once connectivity recovered. But if hard reset fencing action issued, the cluster would have exited the partitioned state after fenced node has been rebooted. Here is a details (logs and spreadsheet) http://goo.gl/Xd4KhQ
I will put more info about freeze policy once ready.