Red Hat Bugzilla – Bug 1413951
Add support for shared storage with sbd
Last modified: 2017-08-01 12:22:40 EDT
Description of problem: SBD provided with RHEL doesn't support usage of shared storage - just watchdog Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Since we don't support sbd on remote-nodes we won't support shared block devices with sbd there either. As with sbd support in general on remote-nodes use of shared block devices there is not explicitly disabled and in fact seems to be working as expected if parameters '-n {remote_node_name}' is added to sbd-config.
Guess documentation has to state that we don't support shared block devices on pacemaker-remote in quite an unambiguous way.
Adding myself as docs contact for release note edit.
Klaus: I updated the description for the release note by adding a title and then adding a sentence to set the context -- that we have added this support. I also included the caveat about support on Pacemaker remote nodes. Does this look ok to you? Steven
When we are going into that degree of details release-note wise we might as well add information that fence-agents package now provides fence_sbd needed to trigger/control the actual fencing by means of a rhcs-style fence-agent. 'poison-pill fencing' is a commonly used and very descriptive term for this kind of fencing. So we might add something like '... enable poison-pill fencing by means ...'. And I guess s/means a shared/means of a shared/. Klaus
(In reply to Klaus Wenninger from comment #0) > > Additional info: When testing with a KVM-VM you can detach the block device. This leads to following message ... May 18 11:32:19 node2 sbd[13165]: /dev/vdb: warning: open_device: Opening device /dev/vdb failed. May 18 11:32:21 node2 sbd[2328]: warning: inquisitor_child: Majority of devices lost - surviving on pacemaker So as long as there is still a cluster visible to sbd it won't suicide. After stopping the other cluster-nodes the suicide will be triggered. Be aware that you don't have no-quorum-action set to suicide because then you won't know if the suicide was triggered via sbd or pacemaker.
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:1933