Bug 994186 - fence_scsi does not work with pacemaker
fence_scsi does not work with pacemaker
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fence-agents (Show other bugs)
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Marek Grac
Cluster QE
Depends On:
Blocks: 987355 994466
  Show dependency treegraph
Reported: 2013-08-06 12:52 EDT by Jaroslav Kortus
Modified: 2013-11-21 02:19 EST (History)
4 users (show)

See Also:
Fixed In Version: fence-agents-3.1.5-32.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 994466 (view as bug list)
Last Closed: 2013-11-21 02:19:26 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jaroslav Kortus 2013-08-06 12:52:36 EDT
Description of problem:
It's not possible to add fence_scsi as a stonith device in pacemaker:
# pcs stonith describe fence_scsi
Stonith options for: fence_scsi
Traceback (most recent call last):
  File "/usr/sbin/pcs", line 110, in <module>
  File "/usr/sbin/pcs", line 96, in main
  File "/usr/lib/python2.6/site-packages/pcs/stonith.py", line 24, in stonith_cmd
  File "/usr/lib/python2.6/site-packages/pcs/stonith.py", line 125, in stonith_list_options
    dom = parseString(metadata)
  File "/usr/lib64/python2.6/site-packages/_xmlplus/dom/minidom.py", line 1925, in parseString
    return expatbuilder.parseString(string)
  File "/usr/lib64/python2.6/site-packages/_xmlplus/dom/expatbuilder.py", line 942, in parseString
    return builder.parseString(string)
  File "/usr/lib64/python2.6/site-packages/_xmlplus/dom/expatbuilder.py", line 223, in parseString
    parser.Parse(string, True)
xml.parsers.expat.ExpatError: mismatched tag: line 20, column 3

The same error repeats when you do pcs stonith create.

I'd also like to raise a question how unfencing should be done with pacemaker and fence_scsi. In cluster.conf we had <unfence> tags for this. I'm unable to find any useful pointer to how this is handled in pacemaker cluster.

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

How reproducible:

Steps to Reproduce:
1. pcs stonith describe fence_scsi

Actual results:

Expected results:
no traceback on any valid operation (describe, create among others)

Additional info:
Comment 3 Marek Grac 2013-08-07 06:54:35 EDT
Fixed in upstream:


Unit test results:

[root@sparta ~]# pcs stonith describe fence_scsi
Stonith options for: fence_scsi
  aptpl: Use APTPL flag for registrations
  devices: List of devices to be used for fencing action
  logfile: File to write error/debug messages
  delay: Wait X seconds before fencing is started
  key: Key value to be used for fencing action
  action: Fencing action
  nodename: Name of node
Comment 6 errata-xmlrpc 2013-11-21 02:19:26 EST
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.


Note You need to log in before you can comment on or make changes to this bug.