Comment 42 for bug 1394188

Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

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