Hello,
I use the old Pacemaker version (1.1.7), and I'm dealing with bug
cl#5072 (monitor op stopping after rsc promotion), which was fixed in
the next Pacemaker version (1.1.8). But due to some reasons I have to
use this and only this version of Pacemaker. Is there any way to avoid
this bug?
Hi,
> It's a boolean, so you can set it with e.g. network-fencing=1 or true.
Already tried, but it didn't worked. The resource was unable to start.
Regards,
Thomas
-Ursprüngliche Nachricht-
Von: Users Im Auftrag von Oyvind Albrigtsen
Gesendet: Mittwoch, 21. November 2018 09:07
An: Clus
On 21/11/18 07:57 +0100, Thomas Berreis wrote:
Hello,
I have a question about stonith configuration within azure and I hope I'm
using the correct mailing list.
I've installed two virtual machines with pacemaker 1.1.18, pcs 0.9.162 and
fence-agents-azure-arm 4.0.11.86.
Now I'm unable to cre
