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
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