Bug 1598031
| Summary: | Tuned fails to isolate the pmd processes with regex by using tuned scheduler [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | tuned | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
| Severity: | high | Docs Contact: | Marek Suchánek <msuchane> |
| Priority: | high | ||
| Version: | 7.4 | CC: | aasmith, atelang, atheurer, fbaudin, jeder, jskarvad, mbabushk, oblaut, olysonek, salmy, skramaja, supadhya, tcerna, thozza, yrachman |
| Target Milestone: | rc | Keywords: | Patch, Upstream, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tuned-2.9.0-1.el7_5.1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, Tuned migrated threads during cores isolation even if you blacklisted the threads from being migrated. With this update, the scheduler plug-in has been fixed to filter thread names through the same blacklist and whitelist filters as process names. As a result, Tuned no longer migrates black listed threads.
|
Story Points: | --- |
| Clone Of: | 1512295 | Environment: | |
| Last Closed: | 2018-08-16 14:20:17 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1512295 | ||
| Bug Blocks: | 1599730, 1601000, 1601001 | ||
|
Description
Oneata Mircea Teodor
2018-07-04 07:56:02 UTC
Veified with puddle OpenStack-13.0-RHEL-7-20180710.3 Kernel 3.10.0-862.6.3.el7 Tuned http://download.eng.bos.redhat.com/brewroot/packages/tuned/2.9.0/1.el7_5.1/noarch/tuned-2.9.0-1.el7_5.1.noarch.rpm Did restart to compute, pmd threads were not evacuated *** Bug 1601350 has been marked as a duplicate of this bug. *** 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-2018:2456 |