Bug 1493976 – CPUAffinity does not accept ranges

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1493976 - CPUAffinity does not accept ranges

Summary:	CPUAffinity does not accept ranges

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	systemd (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	All Linux

Priority	unspecified Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Jan Synacek
QA Contact:	Frantisek Sumsal
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1466365
	Show dependency tree / graph

Reported:	2017-09-21 05:08 EDT by Paul Dwyer
Modified:	2018-04-10 07:23 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	systemd-219-46.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-04-10 07:22:48 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0711	None	None	None	2018-04-10 07:23 EDT

Groups: None (edit)

Description Paul Dwyer 2017-09-21 05:08:56 EDT

Description of problem:
Trying to specify ranges of cpus for CPUAffinity and they are not accepted.
CPUs need to be added individually which is a pain for large cpu systems

Version-Release number of selected component (if applicable):
RHEL7.4
systemd-219-42.el7_4.1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. set the CPUAffinity for systemd in
/etc/systemd/system.conf

2. Trying to set CPUAffinity for a service to other cpus other than default group assigned to systemd in step 1.
Using an override file and specifying cpus in ranges e.g.
CPUAffinity=2-11,24-35,16-23,36-47

3. restart the service and it fails with
Failed at step CPUAFFINITY spawning /usr/sbin/httpd: Invalid argument
exit status=215/affinity 

Actual results:
Service fails to start

Expected results:
Service starts 

Additional info:
Service starts correctly if cpus are listed individually

Doesn't look like systemd supports ranges for CPUAffinity and enforces whitespace as a separator

Comment 2 Jan Synacek 2017-09-25 06:13:01 EDT

We need to backport https://github.com/systemd/systemd/pull/1699.

Comment 3 Jan Synacek 2017-09-27 03:07:44 EDT

https://github.com/lnykryn/systemd-rhel/pull/149

Comment 11 Lukáš Nykrýn 2017-10-08 02:10:18 EDT

fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/149 -> post

Comment 17 errata-xmlrpc 2018-04-10 07:22:48 EDT

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:0711

Note You need to log in before you can comment on or make changes to this bug.