When a node has set RECOVERY_ACTIVE, e.g. by triggering an election, and then banned itself (or got banned), then the databases won't be freezing, and hence the node will remain in banned state indefinitely even if the reason for banning has been fixed. This can for instance happen if a node-internal interface is brought down on a non-recmaster node. Only a ctdb restart can fix this situation. This is a regression from 4.3, introduced with b4357a79d916b1f8ade8fa78563fbef0ce670aa9 and d8f3b490bbb691c9916eed0df5b980c1aef23c85
Created attachment 12157 [details] patch for master that is in autobuild currently This patch has come out of the discussion between Amitay, Martin and me and is currently in autobuild.
Created attachment 12162 [details] patch for v4-4-test, cherry-picked from master Patch for 4.4, cherry-picked with one minor context-resolution from master.
Comment on attachment 12162 [details] patch for v4-4-test, cherry-picked from master LGTM!
Karolin, all yours. :)
Comment on attachment 12162 [details] patch for v4-4-test, cherry-picked from master LGTM
(In reply to Guenther Deschner from comment #5) Pushed to autobuild-v4-4-test.
(In reply to Karolin Seeger from comment #6) Pushed to v4-4-test. Closing out bug report. Thanks!