Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionKlaus 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.
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