Comment 3 for bug 1331450

Revision history for this message
Sergii Golovatiuk (sgolovatiuk) wrote :

This issue should go away after upgrading Corosync to 2.X. Since we are in feature freeze, corosync 2.x packages will be added to 6.1