stonith-timeout and stonith-action properies are ignored when running pcs stonith fence command in a Pacemaker cluster

Solution Unverified - Updated

Environment

  • Red Hat Enterprise Linux 6 (with the High Availability Add-on)
  • Red Hat Enterprise Linux 7 (with the High Availability Add-on)
  • Red Hat Enterprise Linux 8 (with the High Availability Add-on)
  • Pacemaker

Issue

  • The stonith-timeout and stonith-action cluster properties only apply to stonith actions (on/off/reboot) created by the Pacemaker scheduler.
  • stonith-timeout and stonith-action do not apply to fencing by the stonith_admin or pcs stonith fence <node> commands.
  • Why did my fence test time out even after I increased stonith-timeout?
  • Why did my fence test reboot a node even after I set stonith-action=off?

Resolution

Red Hat Enterprise Linux 6


There are no plans to fix this issue in RHEL 6. See [workaround](#workaround).

Red Hat Enterprise Linux 7


This issue was being tracked in [Bug 1461377 - Make manual fencing via stonith_admin use same timeout as configured in CIB [RHEL 7]](https://bugzilla.redhat.com/show_bug.cgi?id=1461377). As of 21 February 2020, this bug is in CLOSED_WONTFIX state. Due to developer time constraints, there are no plans to fix this in RHEL 7.

Red Hat Enterprise Linux 8


This issue is being tracked in [Bug 1693256 - Make manual fencing via stonith_admin use same timeout as configured in CIB [RHEL 8]](https://bugzilla.redhat.com/show_bug.cgi?id=1693256). As of 29 October 2019, this bug is in ASSIGNED state.

If you would like to track the progress of this bug, please This content is not included.open a case with Red Hat Global Support Services.

Workaround


Configure the [`pcmk_reboot_timeout`](/documentation/en-us/red_hat_enterprise_linux/7/html-single/high_availability_add-on_reference/index#tb-fencepropsadvanced-HAAR) attribute for each stonith device.

Root Cause

When Pacemaker's policy engine creates a transition with a fencing request, the stonith daemon uses the timeout value that is passed by the transition engine. This matches the value of the stonith-timeout cluster property.

When fencing is triggered manually via stonith_admin or pcs stonith fence, the default timeout implemented in stonith_admin (120s) is used instead.

SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.