-
Bug
-
Resolution: Unresolved
-
Major
-
4.14.0
-
Important
-
No
-
CNF Compute Sprint 242, CNF Compute Sprint 243, CNF Compute Sprint 244, CNF Compute Sprint 245
-
4
-
Rejected
-
False
-
-
bug fix text
-
Bug Fix
-
In Progress
-
-
-
Description of problem:
Current when the Guaranteed pods is started with cpu load balancing is disabled the cpus allocated are removed from joining any scheduling domains. but after the pod is deleted, the cpus do not go back to it's original configuration
Version-Release number of selected component (if applicable):
4.14.0-0.ci-2023-08-11-000617
How reproducible:
Not everytime but does happen
Steps to Reproduce:
1. Create a guaranteed(gu) pod with cpu-load-balancing.crio.io: "disable" annotation 2. After the pods is running state, check the cpus alloted to the pod 3. Check /proc/schedstat and verify the cpus used by gu pod are not part of scheduling domains 4. Delete the pod 5. Verify /proc/schedstat is updated (even after waiting for long time it doesn't get updated , i.e cpus used by gu pod should be part of scheduling domains 6. Verify any burstable pod and check it's cpuset.cpus , they should have the cpus that were used by gu pod, added back to it's cpuset.
Actual results:
5. Verify /proc/schedstat is updated (even after waiting for long time it doesn't get updated , i.e cpus used by gu pod should be part of scheduling domains 6. Verify any burstable pod and check it's cpuset.cpus , they should have the cpus that were used by gu pod, added back to it's cpuset. This doesn't happen.
Expected results:
5. Verify /proc/schedstat is updated i.e cpus used by gu pod should be part of scheduling domains 6. Verify any burstable pod and check it's cpuset.cpus , they should have the cpus that were used by gu pod, added back to it's cpuset.
Additional info:
- is cloned by
-
-
- New
-