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.
Bug 1897087 - spausedd lacks capability to move to root cgroup [rhel-7.9.z]
Summary: spausedd lacks capability to move to root cgroup [rhel-7.9.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: corosync
Version: 7.9
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jan Friesse
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1897085
Blocks: 1906822
TreeView+ depends on / blocked
 
Reported: 2020-11-12 09:45 UTC by Reid Wahl
Modified: 2024-03-25 17:02 UTC (History)
8 users (show)

Fixed In Version: corosync-2.4.5-7.el7_9.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1897085
: 1906822 (view as bug list)
Environment:
Last Closed: 2021-02-02 12:07:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 5574661 0 None None None 2020-11-13 05:13:20 UTC

Description Reid Wahl 2020-11-12 09:45:45 UTC 
+++ This bug was initially created as a clone of Bug #1897085 +++

Description of problem:

If CPU accounting is enabled, then spausedd is not allowed to run with SCHED_RR priority without additional cgroup configuration. corosync works around this issue by moving itself to the root cgroup by default if it's not already in the root cgroup path. (See BZ 1476214 and corosync_move_to_root_cgroup().)

spausedd lacks such capability. So if CPU accounting is enabled, spausedd fails to obtain SCHED_RR priority unless a user has explicitly added cgroup configs to allow RT scheduling for spausedd.

spausedd should have the same "move to root cgroup" behavior as corosync.

This has been added upstream in the following commit:
  - https://github.com/jfriesse/spausedd/commit/21836a25

-----

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

spausedd-2.4.5-7.el7

-----

How reproducible:

Always

-----

Steps to Reproduce:
1. Enable CPU accounting. One way to do this is to set DefaultCPUAccounting=yes in /etc/systemd/system.conf. More details in https://access.redhat.com/articles/3696121.
2. Reboot.
3. Start spausedd.service.

-----

Actual results:

If BZ 1896311 has not been fixed, spausedd crashes with SIGSEGV.

If BZ 1896311 has been fixed, spausedd starts up and logs the error "Operation not permitted (1): Can't set SCHED_RR".

-----

Expected results:

spausedd starts normally and obtains SCHED_RR priority.
Comment 2 Jan Friesse 2020-11-12 17:31:44 UTC 
Patch: https://github.com/jfriesse/spausedd/commit/21836a25

Reproducer is in the first comment.
Comment 12 errata-xmlrpc 2021-02-02 12:07:40 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 (corosync 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:0349
Note You need to log in before you can comment on or make changes to this bug.