Min Li
Min Li
The contents of /etc/crio/crio.conf.d/01-workload-partitioning is not correct, the line 59 should be: [crio.runtime.workloads.management.resources] cpushares = 0 CPUs = "0-1, 52-53" I have tested, only using this format can lead to...
yeah, just delete the blank line，like： [crio.runtime.workloads.management] activation_annotation = "target.workload.openshift.io/management" annotation_prefix = "resources.workload.openshift.io" [crio.runtime.workloads.management.resources] cpushares = 0 CPUs = "0-1, 52-53"
And line 37 should changed to: source: data:text/plain;charset=utf-8;base64,W2NyaW8ucnVudGltZS53b3JrbG9hZHMubWFuYWdlbWVudF0KYWN0aXZhdGlvbl9hbm5vdGF0aW9uID0gInRhcmdldC53b3JrbG9hZC5vcGVuc2hpZnQuaW8vbWFuYWdlbWVudCIKYW5ub3RhdGlvbl9wcmVmaXggPSAicmVzb3VyY2VzLndvcmtsb2FkLm9wZW5zaGlmdC5pbyIKW2NyaW8ucnVudGltZS53b3JrbG9hZHMubWFuYWdlbWVudC5yZXNvdXJjZXNdCmNwdXNoYXJlcyA9IDAKQ1BVcyA9ICIwLTEsIDUyLTUzIgo=
In pre-merge test, I can verify the Atomic locking take effect between /proc/irq/default_smp_affinity and /etc/sysconfig/irqbalance. But when I verify container replacement, crio didn't generate logs like below: msg="Container \"05ed1c9d704e2e478779ac6fadc5ba32c9c085642cfb4215d2d65ada7e33efba\" (\"k8s_qos-demo-ctr-1_qos-demo-f94c57b6d-kjvnz_default_161bac87-672a-4b84-9e14-673806b51e33_0\")...
Yeah, I did set crio log level as debug.