>>> Nikola Ciprich <[email protected]> schrieb am 21.03.2022 um 10:31 in Nachricht <[email protected]>: > Hello dear fellow pacemaker users and developers, > > we've recently experienced unplanned outages caused by failure > to stop rather unimportant resource.. This was caused by default > setting to fence the node on failing stop operation. > > While we'll investigate further those stop failures, I'd still > like to change this setting. We're perfectly fine with resource to > remain hanging in failed state when this happens, we'll see this > in monitoring and act accordingly. However setting on‑fail action > to block also prevents restarting resources on their crash, which > is not what we want... Is there a way to disable fence for stop > failures, but to keep other behaviour as it is?
Just add an "on-fail=" for the stop operation (e.g. on_fail=block). > > maybe I'm missing something obvious? > > thanks a lot in advance! > > with best regards > > nik > > > ‑‑ > ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ > Ing. Nikola CIPRICH > LinuxBox.cz, s.r.o. > 28.rijna 168, 709 00 Ostrava > > tel.: +420 591 166 214 > fax: +420 596 621 273 > mobil: +420 777 093 799 > www.linuxbox.cz > > mobil servis: +420 737 238 656 > email servis: [email protected] > ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑ > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
