isolcpu interactions with non-guaranteed pods
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
David Sullivan |
Bug Description
Brief Description
-----------------
isolcpu's does not play nice with besteffort or burstable pods.
With isolcpu's enabled these pods will get stuck on the core where they were first scheduled vs floating. Overlaying exlusive cpu's with this, one can end up in a situation where the besteffort/
There will always be some besteffort or burstable pods on a worker node as the system pods (calico et) fall into the category.
So for worker nodes that do not have the openstack-compute label assigned we need to remove the isolcpu's boot arg. I believe the change would be at line 581 in platform.py plugin.
Severity
--------
Major
Steps to Reproduce
------------------
Launch pods with exclusive CPU's
Expected Behavior
------------------
Pods using defaultCpuSet should be able to float across that set
Actual Behavior
----------------
See description
Reproducibility
---------------
100%
System Configuration
-------
Low-latency worker
Branch/Pull Time/Commit
-------
BUILD_
Last Pass
---------
Never
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Other
Marking as release gating; high priority as this can result in stability and performance issues for the containerized env