This issue happened due to change of cluster stack version to corosync 2.x invalid for pre-6.1 versions
This issue happened due to change of cluster stack version to corosync 2.x invalid for pre-6.1 versions