RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1470262 - disabling a fencing-device that has queued actions leads to stonithd receiving SIGABRT
Summary: disabling a fencing-device that has queued actions leads to stonithd receivin...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: 7.5
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1481141
TreeView+ depends on / blocked
 
Reported: 2017-07-12 15:43 UTC by Klaus Wenninger
Modified: 2020-12-14 09:06 UTC (History)
8 users (show)

Fixed In Version: pacemaker-1.1.18-1.el7
Doc Type: Bug Fix
Doc Text:
Previously, if a fencing device configured with the pcmk_delay_max setting was disabled while a fencing action was being delayed, Pacemaker's stonithd service attempted to free memory used for the action twice. As a consequence, Pacemaker terminated unexpectedly. With this update, stonithd has been fixed to free the memory only once, and as a result, the described problem no longer occurs.
Clone Of:
: 1481141 (view as bug list)
Environment:
Last Closed: 2018-04-10 15:30:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1474905 0 medium CLOSED stonith: dynamic enabling/disabling of stonith resources by rule-constraints 2023-09-14 04:01:35 UTC
Red Hat Product Errata RHEA-2018:0860 0 None None None 2018-04-10 15:32:11 UTC

Internal Links: 1474905

Description Klaus Wenninger 2017-07-12 15:43:59 UTC 
Description of problem:
When a stonith-action is being delayed by pcmk_delay_max (or the new upstream attribute pcmk_delay_base) and the stonith-device is being disabled within
this waiting time stonith coredumps because it receives SIGABRT.

Version-Release number of selected component (if applicable):
1.1.17

How reproducible:
100%

Steps to Reproduce:
1. setup fencing with a fencing-device that has attribute pcmk_delay_max or pcmk_delay_base (just supported with upstream-master at that time)
2. trigger fencing of a node with e.g. pcs
3. use pcs to disable the fencing-resource while the delay configured is running

Actual results:
stonithd core dumps
the pcs-command for fencing is running into a timeout as the communication partner has died

Expected results:
no core dump
immediate failure result of pcs fencing command

Additional info:
Already fixed upstream
https://github.com/ClusterLabs/pacemaker/commit/e7027e9d303be5e3f9531c0cb0ef8af914f2adda
Comment 6 Patrik Hagara 2017-12-07 16:29:12 UTC 
Tested as per comment 1:
 * create stonith resource with pcmk_delay_max set to 300 seconds
 * start a fence operation ("pcs stonith fence ...")
 * while the fence operation is being delayed, run "pcs stonith disable ..."

Before the fix (1.1.16-12.el7):
 * the fence operation returns non-zero after almost double the pcmk_delay_max (eg. 564 seconds) with the message:
> Error: unable to fence 'virt-156'
> Command failed: Timer expired
 * the "pcs stonith disable ..." command hangs (likely) indefinitely
 * stonithd received SIGABRT on the node performing the fence operation
 * no node got fenced
 * node on which stonithd crashed transitions into "UNCLEAN (Online)" cluster membership status
 * fence resource marked as "FAILED (disabled)"

After the fix (1.1.18-1.el7):
 * the fence operation returns non-zero immediately with:
> Error: unable to fence 'virt-164'
> Command failed: No route to host
 * the "pcs stonith disable ..." command completes successfully
 * stonithd does not crash and no other crashes are detected by abrt
 * no node got fenced
 * all nodes are in a clean online cluster membership state
 * fence resource marked as "Stopped (disabled)"

Marking verified.
Comment 7 Patrik Hagara 2017-12-07 16:33:54 UTC 
Just to clarify the first point in "after the fix" should read:

 * the fence operation returns non-zero immediately __after "pcs stonith disable ..." completes__ with:
Comment 10 errata-xmlrpc 2018-04-10 15:30:29 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0860
Note You need to log in before you can comment on or make changes to this bug.