-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.14
-
None
-
+
-
Important
-
No
-
CNF Compute Sprint 250, CNF Compute Sprint 251
-
2
-
False
-
-
-
Bug Fix
-
In Progress
-
Description of problem:
This is only applicable to systems that install a performance profile There seems to be a race condition where all systemd spawed processes are not being moved to /sys/fs/cgroup/cpuset/system.slice. This is suppose to be done by the one-shot cpuset-configure.service. Here is a list of processes I see on one lab that are still in the root directory /usr/bin/dbus-broker-launch --scope system --audit dbus-broker --log 4 --controller 9 --machine-id 071fd738af0146859d2c04b7fea6d276 --max-bytes 536870912 --max-fds 4096 --max-matches 131072 --audit /usr/sbin/NetworkManager --no-daemon /usr/sbin/dnsmasq -k /sbin/agetty -o -p -- \u --noclear - linux sshd: core@pts/0
Version-Release number of selected component (if applicable):
4.14, 4.15
How reproducible:
Steps to Reproduce:
1. Reboot a SNO with a peformance profile applied 2. 3.
Actual results:
Expected results:
Additional info:
- blocks
-
OCPBUGS-31692 Systemd processes not being moved to cpuset/systemd.slice
- Closed
- is cloned by
-
OCPBUGS-31692 Systemd processes not being moved to cpuset/systemd.slice
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update