Failed to allocate guaranteed pods to non-isolated CPU
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Boovan Rajendran |
Bug Description
Brief Description
For k8s 1.26 when we create a pod of guaranteed QOS after setting CPU manager policy as static the pod should be allocated to non-isolated CPU instead it is allocated to isolated CPU.
Severity
Major
Steps to Reproduce
1. Set up the "kube-cpu-
system host-lock controller-0
system host-label-assign --overwrite controller-0 kube-cpu-
system host-cpu-modify -f application-
system host-unlock controller-0
2. Create a guaranteed pod with isolcpus specified.
Expected Behavior
Pod should be allocated to non-isolated CPU.
Actual Behavior
Pod is allocated to isolated CPU.
Reproducibility
100%
System Configuration
AIO-SX
Last Pass
NA
Timestamp/Logs
NA
Alarms
NA
Test Activity
Developer Testing
Workaround
NA
Changed in starlingx: | |
assignee: | nobody → Boovan Rajendran (brajendr) |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.9.0 stx.containers |
Fix proposed to branch: master /review. opendev. org/c/starlingx /integ/ +/900148
Review: https:/