This bug is a duplicate and is related to corosync bugs. We are going to address it by corosync upgrade to version 2.x
This bug is a duplicate and is related to corosync bugs. We are going to address it by corosync upgrade to version 2.x