On Mon, Jan 03, 2022 at 10:14:48 +0100, Peter Krempa wrote:

On Wed, Dec 29, 2021 at 17:56:57 +0000, lejeczek wrote:

...

Hi guys.

Is it possible to allow 'unsafe' migration globally?

No there's no global switch for this and there won't be one as there are multiple reasons why migration can be unsafe.

Additionally, would you mind describing your setup and why you even need unsafe? Maybe there's a gap that we can fix.

On Wed, Jan 5, 2022 at 2:25 PM lejeczek <peljasz@yahoo.co.uk> wrote:

I think there is a quite urgent problem needing a repair fast, I described it here: https://bugzilla.redhat.com/show_bug.cgi?id=2037218 I was hoping, perhaps over-optimistically, for something I could try as a 'quick' workaround.

thanks, L.

I think GlusterFS usage in pacemaker clusters is not so common (eg, I don't know if it is supported at all in RH EL clusters). It is not so clear to me if you configured GlusterFS outside of pacemaker or not: in fact through a quick search I found both types of attempts around... Probably inside the bugzilla you should precisely outline your configuration and in case of embedding GlusterFS as a resource, what is you pacemaker configuration, so how your configured your resources/clones (eg ocf:glusterfs:glusterd, ocf:glusterfs:volume, ecc..), so that it easily reproducible Personally I never used GlusterFS with Pacemaker Gianluca