Bug 1768906

Summary:	ci covers solely cmdline-usage reading/writing storage
Product:	Red Hat Enterprise Linux 8	Reporter:	Klaus Wenninger <kwenning>
Component:	sbd	Assignee:	Klaus Wenninger <kwenning>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	cfeist, cluster-maint, mmazoure, nhostako
Target Milestone:	rc
Target Release:	8.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	sbd-1.4.1-2.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 15:56:20 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:	1769305
Bug Blocks:

Description Klaus Wenninger 2019-11-05 14:02:56 UTC

Description of problem:

CI for sbd tests reading/writing communication-slots on storage using the sbd-binary as cmdline-tool.
This is an essential part of sbd being e.g. used by fence_sbd fence-agent & pcs.
Counterpart is usually the sbd-daemon (same executable run in daemon-mode) watching out for changes in pacemaker-node-status and messaging-slots on shared storage being observed by a hardware-watchdog.
In watchdog-fencing-mode shared storage isn't used at all.
So what is missing is testing the behaviour of sbd running as a daemon.


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


How reproducible:

100%


Steps to Reproduce:
1. build using rhpkg
2.
3.

Actual results:

CI wouldn't detect any misbehaviour in daemon-mode like not properly setting up the watchdog, improper handling of timeouts while unsuccessfully trying to access pacemaker-cib or shared storage, not detecting issues with shared-storage, ... 


Expected results:

Run sbd as daemon as well in CI and check for proper watchdog-management, failure-detection on shared-disk, response to messages passed via messaging-slots, timeout-handling in mainloop, timeout-actions triggered ...


Additional info:

Up to now CI as well needs losetup and dmsetup both requiring priviledged conainers or bare-metal setups which might be troublesome in the future.
Already now this is the reason why tests can't be run as part of mock-build already.

Comment 1 Klaus Wenninger 2019-11-05 14:28:20 UTC

Everything needed is available upstream since merge of following pull-request

https://github.com/ClusterLabs/sbd/pull/101

Comment 6 errata-xmlrpc 2020-04-28 15:56:20 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-2020:1667