From 352dfaba0ef65fd81ede289864d27f26dd95309c Mon Sep 17 00:00:00 2001 From: Krisztian Litkey Date: Fri, 17 Jun 2022 00:27:23 +0300 Subject: [PATCH] test/e2e: don't use invalid '0' CPU reservation. Don't use invalid 'cpu: 0' CPU reservation (the correct syntax for picking an exact CPU would be 'cpu: cpuset:0). Use the same 'CPU: 750m' as we use in the default config. --- .../n4c16/test00-basic-placement/cri-resmgr.cfg.in | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/test/e2e/policies.test-suite/topology-aware/n4c16/test00-basic-placement/cri-resmgr.cfg.in b/test/e2e/policies.test-suite/topology-aware/n4c16/test00-basic-placement/cri-resmgr.cfg.in index 8e9478abd..fb4b21d58 100644 --- a/test/e2e/policies.test-suite/topology-aware/n4c16/test00-basic-placement/cri-resmgr.cfg.in +++ b/test/e2e/policies.test-suite/topology-aware/n4c16/test00-basic-placement/cri-resmgr.cfg.in @@ -1,9 +1,11 @@ policy: Active: topology-aware ReservedResources: - cpu: 0 + CPU: 750m topology-aware: ColocatePods: $(echo ${COLOCATE_PODS:-false}) ColocateNamespaces: $(echo ${COLOCATE_NAMESPACES:-false}) logger: Debug: cri-resmgr,resource-manager,cache,policy + Klog: + skip_headers: true