Bug 1324240

Summary:	Rebase to sync sbd with upstream
Product:	Red Hat Enterprise Linux 7	Reporter:	Klaus Wenninger <kwenning>
Component:	sbd	Assignee:	Klaus Wenninger <kwenning>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	cfeist, jkortus, kgaillot, mnovacek, royoung
Target Milestone:	rc	Keywords:	Rebase
Target Release:	7.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	sbd-1.2.1-20.el7	Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:		Story Points:	---
Clone Of:
Clones:	1337236 (view as bug list)		Environment:
Last Closed:	2016-11-04 03:04:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1337236

Description Klaus Wenninger 2016-04-05 23:03:09 UTC

Description of problem:

SBD is not a super active upstream project but recently there had been
a couple of interesting changes that interfere with a lot of files
like stuff for pacemaker-remote and clarification of licensing in
most of the files.
So it is much cleaner and easier to support to base on the 
upstream version and patch what we want differently (like e.g. not
supporting block-devices for now) instead of doing it the other
way round.

Comment 3 michal novacek 2016-09-27 12:59:34 UTC

In our internal testing the following scenarios do work:

  * sbd as the only mean of fencing
    (internally: pacemaker,recovery,recovery-all,sbd,sbd-only,kill_sysrq_panic)
  * sbd as the secondary fencing, where the primary fencing works
    (internally: pacemaker,recovery,recovery-all,sbd,sbd-with-other-fencing,kill_sysrq_panic)
  * sbd as the secondary fencing, where the primary fencing never works (/bin/false)
    (internally: pacemaker,recovery,recovery-all,sbd,sbd-with-fake-fencing,kill_sysrq_panic)

It means that the following expected recovery behaviour of the cluster occurs
in the follwing scenarios:
    * killing node where the resource is active
    * causing one node to fall off the network
    * causing switch failure (nodes do not see each other)
    * killing random (one or more) node:
        * less than quorum
        * more than quorum
    * killing pacemaker on one or more nodes


Marking verified.

Comment 5 errata-xmlrpc 2016-11-04 03:04:53 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://rhn.redhat.com/errata/RHBA-2016-2306.html