Your message dated Wed, 01 Feb 2023 08:13:14 +0100
with message-id <[email protected]>
and subject line Re: Bug#970084: corosync: Corosync becomes unresponsive and
disconnects from the rest of the cluster when primary link is lost
has caused the Debian Bug report #970084,
regarding Unrecoverable split.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
970084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970084
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: corosync
Version: 3.0.1-2+deb10u1
Severity: wishlist
Dear Maintainer,
it seems that in version 3.0.1 of corosync there's a bug which causes
unrecoverable splits; it seems that it had been corrected in 3.0.3. Please
see Github issue #506.
-> https://github.com/corosync/corosync/issues/506
The issue is unclear if the bug is in corosync or in Kronosnet, and it
seems to suggests to use at least library version 1.13. Besides in
buster-backports there's already version 1.16.
Please could the upgrade to newer version of corosync be considered ? It
should also require a dependency on the same version of
"libknet" in backports.
Thank you for your interest in the issue.
Regards.
--- End Message ---
--- Begin Message ---
This bug affects only oldstable (buster), where the suggested fix is to
upgrade libknet1 from backports to 1.16-2~bpo10+1.
--- End Message ---
