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.

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

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

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

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

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