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.

Created attachment 1584087 [details]
avc-logs on sbd startup

Description of problem:

When trying to reproduce the rt-scheduling related denials found with Comment #15 of https://bugzilla.redhat.com/show_bug.cgi?id=1715134 with an installation based on the nightly-build of 2019-06-21 I wasn't able to identify those denials stated there but saw multiple others never seen before.
Versions of sbd & selinux-policy are as with bz1715134.


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

1.14.3-9.el8

How reproducible:

100%

Steps to Reproduce:
1. enable sbd
2. start pacemaker
3.

Actual results:

See attachment

Expected results:

No denials

Additional info:

Klaus,

Does the service start successfully in SELinux enforcing mode or does it (or something else) fail?

Which authentication method is in place, is it sudo?

Zdenek,

The service seems to start properly.
If I check rt-prio afterwards it seems to be set properly on the sbd-processes.
But that is to be expected somehow as the denials don't seem in areas relevant
for sbd.

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-2019:3547