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.

Description of problem: Several users (including myself, a number of times) have experienced problems with pcmk_host_list due to its lack of support for semi-colon as a delimiter.  I think the confusion mostly comes from the fact that pcmk_host_map does allow it, so users that are familiar with that parameter may be inclined to use a semi-colon in both out of habit.  That's certainly what my problem was until I discovered it doesn't work, and we've had a few customers do the same thing.

We should add support for semi-colon when parsing pcmk_host_list to avoid unexpected failures to fence.  


Version-Release number of selected component (if applicable): pacemaker-1.1.12-22.el7


How reproducible: Always


Steps to Reproduce:
1. Create a stonith device with a semi-colon delimiter in pcmk_host_list="node1;node2"

2. Create a reason for a node to be fenced


Actual results:  Nodes don't see that device as being eligible to fence this node:

  Mar 26 09:50:26 rhel7-node1 stonith-ng[3392]: notice: can_fence_host_with_device: kdump can not fence (reboot) rhel7-node2.example.com: static-list


Expected results: Node is fenced


Additional info:

Upstream pull request at: 

  https://github.com/ClusterLabs/pacemaker/pull/671

Tested successfully.

Patch merged

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://rhn.redhat.com/errata/RHSA-2015-2383.html