Comment 4 for bug 1331450

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

This bug is invalid as we switched to corosync 2.0. I cannot see such warnings anymore.