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-05-22 17:20:07 UTC
+++ This bug was initially created as a clone of Bug #1713021 +++
Description of problem:
If CPUAccounting is enabled sbd isn't able to set rt-priority for its processes.
Version-Release number of selected component (if applicable):
1.3.1-18.el8
How reproducible:
100%
Steps to Reproduce:
1. Setup a cluster that uses sbd
2. Prior to starting cluster on one node (corosync and sbd still down) issue:
'systemctl --runtime set-property system.slice CPUAccounting=true'
3. systemctl start pacemaker
Actual results:
'systemctl status sbd' prints
...
May 22 18:48:15 node4 sbd[2398]: error: sbd_make_realtime: Unable to set scheduler priority to 99: Operation not permitted (1)
...
Using top or ps one can as well verify that the sbd-processes aren't rt scheduled.
Expected results:
sbd-processes should be rt-schedules as expected.
[root@node2 ~]# top -b|grep sbd
1218 root rt 0 126332 19952 18192 S 0.0 1.1 0:00.00 sbd
1219 root rt 0 142116 33448 29580 S 0.0 1.8 0:00.15 sbd
1220 root rt 0 142616 35992 30600 S 0.0 2.0 0:00.02 sbd
Additional info:
Amongst those components that enable CPUAccounting are e.g.
Red Hat Insights, Docker, ...
--- Additional comment from Klaus Wenninger on 2019-05-22 17:19:09 UTC ---
This could as well be assigned to e.g. systemd or another basic configuration component.
The discussion of this topic is controversial and it doesn't look as if there would be a clean and easy to access solution anytime soon.
Corosync meanwhile has gone a slightly hacky approach for the same problem.
This it probably makes sense to target a similar implementation in sbd as well to first have a solution that doesn't require additional configuration and to be consistent within the cluster-suite.
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:0995