Bug 1441791
| Summary: | cpu-partitioning: systemd error when applying CPUAffinity= | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Luiz Capitulino <lcapitulino> |
| Component: | tuned | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED ERRATA | QA Contact: | Tereza Cerna <tcerna> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | jeder, jskarvad, lcapitulino, tcerna |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tuned-2.8.0-2.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 12:35:21 UTC | Type: | Bug |
| 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: | |||
| Bug Blocks: | 1394932 | ||
|
Description
Luiz Capitulino
2017-04-12 17:59:14 UTC
Already fixed on upstream:
commit 3023c9e86090508602d9b9d55dcc94cef3cf9e7c
Author: Jaroslav Škarvada <jskarvad>
Date: Tue Apr 11 19:28:59 2017 +0200
systemd: added support for older systemd CPUAffinity syntax
(In reply to Luiz Capitulino from comment #2) > Already fixed on upstream: > > commit 3023c9e86090508602d9b9d55dcc94cef3cf9e7c > Author: Jaroslav Škarvada <jskarvad> > Date: Tue Apr 11 19:28:59 2017 +0200 > > systemd: added support for older systemd CPUAffinity syntax Thanks for info. I would like to do respin. When using tuned-2.8.0-2.el7, I can see that the systemd configuration file doesn't contain commas and I don't see any systemd error on dmesg. So, this issue is fixed. @Luiz: Thank you for your testing. Switching to VERIFIED (SanityOnly) status based on successful test by lcapitulino. 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:2102 |