Unable to dynamically change cpuset.cpus for container image
Issue
After "hot-adding" CPUs to an Atomic host on reboot, containers previously created have only assigned the original CPU list in their cpuset.cpus file, and do not make use of the new CPUs
Environment
- Red Hat Enterprise Linux Atomic Host 7.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.