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 1481141 - disabling a fencing-device that has queued actions leads to stonithd receiving SIGABRT [rhel-7.4.z]
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.4
Assignee: Ken Gaillot
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1470262
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-14 08:26 UTC by Oneata Mircea Teodor
Modified: 2020-12-14 09:30 UTC (History)
10 users (show)

Fixed In Version: pacemaker-1.1.16-12.el7_4.1
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: 1470262
Environment:
Last Closed: 2017-09-05 11:31:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2587 0 normal SHIPPED_LIVE pacemaker bug fix update 2017-09-05 15:20:01 UTC

Description Oneata Mircea Teodor 2017-08-14 08:26:06 UTC 
This bug has been copied from bug #1470262 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 2 Ken Gaillot 2017-08-15 15:50:43 UTC 
Testing procedure:

1. Configure a cluster of at least two nodes and a fencing device with a long pcmk_delay_max setting.

2. Initiate fencing of one node via pcs, then immediately disable the fence device.

Before the fix, stonithd will core dump, and pcs will time out. After the fix, stonithd will not core dump, and pcs will immediately return an error (because the device is no longer usable).

Because pcmk_delay_max uses a random delay, it may not be obvious whether the fence device was disabled before the delay expired. You can check the logs to see what order things happened in.
Comment 6 errata-xmlrpc 2017-09-05 11:31:54 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/RHBA-2017:2587
Note You need to log in before you can comment on or make changes to this bug.