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.

Description of problem:

For making start/stop synchronization between pacemaker & sbd the default (bz1873135 & bz1873138) it would be cleaner to be able to make pacemaker conflict with sbd version < 1.4.2 instead of some release.
Apart from that we have most of the changes since 1.4.1 anyway already in as patches so actual code change/risk would be minimal.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Changes coming with the rebase compared to the lates rhel-8.3 build are minimal:

- sanity check of device-name(s) given as shared disk(s)
- sbc.pc in package
- overhaul of the code that set scheduling
  basically robustness with future changes of kernel-config
  and sets SCHED_OTHER prio as high as possible if setting SCHED_RR fails (shouldn't happen anyway on production config)
- print a hint to restart sbd-service after disk-initialization

Everything else is just CI related and has no influence on the content of the rpm.
And there is of course the default for sbd-syncing switched to enabled in the spec-file - not rebase related.

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 (sbd bug fix and enhancement update), 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-2021:1874