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 1477461 - running docker containers prevents processes to use real-time scheduling when restarted [rhel-7.4.z]
Summary: running docker containers prevents processes to use real-time scheduling when...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: corosync
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Jan Friesse
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1476214
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-02 07:40 UTC by Oneata Mircea Teodor
Modified: 2017-09-05 11:24 UTC (History)
30 users (show)

Fixed In Version: corosync-2.4.0-9.el7_4.1
Doc Type: Bug Fix
Doc Text:
Previously, when the corosync service was started or restarted after systemd enabled CPU Accounting, corosync was not able to run with Real Time (RT) scheduling priority. This in some cases reduced the stability of the High Availability (HA) cluster. This update moves corosync to the root CPU cgroup by default and now, corosync can run with Real Time priority as expected.
Clone Of: 1476214
Environment:
Last Closed: 2017-09-05 11:24:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Proposed patch 1 (6.35 KB, patch)
2017-08-02 11:18 UTC, Jan Friesse 		no flags Details | Diff
Proposed patch 2 (8.43 KB, patch)
2017-08-02 11:18 UTC, Jan Friesse 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2570 0 normal SHIPPED_LIVE corosync bug fix update 2017-09-05 15:17:18 UTC

Description Oneata Mircea Teodor 2017-08-02 07:40:33 UTC 
This bug has been copied from bug #1476214 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 2 Jan Friesse 2017-08-02 11:18:05 UTC 
Created attachment 1308124 [details]
Proposed patch 1
Comment 3 Jan Friesse 2017-08-02 11:18:40 UTC 
Created attachment 1308125 [details]
Proposed patch 2
Comment 7 errata-xmlrpc 2017-09-05 11:24:10 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, 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-2017:2570
Note You need to log in before you can comment on or make changes to this bug.