-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.13, 4.12.z, 4.11.z, 4.10.z
-
Important
-
Yes
-
CNF RAN Sprint 235, CNF RAN Sprint 236, CNF RAN Sprint 237, CNF RAN Sprint 238
-
4
-
False
-
-
-
Description of problem:
addon-agent and proxy-agent containers in pod cluster-proxy-proxy-agent-xxxx are not pinned to reserved management cores. klusterlet container in pod klusterlet-xxxxx is also not pinned to reserved management cores.
Version-Release number of selected component (if applicable):
oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.0-rc.2 True False 5d4h Cluster version is 4.13.0-rc.2
How reproducible:
Always
Steps to Reproduce:
1. Deploy SNO via ZTP with workload partitioning enabled 2. Check mgmt pods affinity 3.
Actual results:
pods do not have workload partitioning annotation, and are not pinned to mgmt cores
Expected results:
All management pods should be pinned to reserved cores Pod should be annotated with: target.workload.openshift.io/management: '{"effect":"PreferredDuringScheduling"}'
Additional info:
cluster-proxy-proxy-agent pod annotations metadata apiVersion: v1 kind: Pod metadata: annotations: k8s.ovn.org/pod-networks: '{"default":{"ip_addresses":["10.128.1.154/23"],"mac_address":"0a:58:0a:80:01:9a","gateway_ips":["10.128.0.1"],"ip_address":"10.128.1.154/23","gateway_ip":"10.128.0.1"}}' k8s.v1.cni.cncf.io/network-status: |- [{ "name": "ovn-kubernetes", "interface": "eth0", "ips": [ "10.128.1.154" ], "mac": "0a:58:0a:80:01:9a", "default": true, "dns": {} }] openshift.io/scc: restricted-v2 proxy.open-cluster-management.io/configuration-generation: "1" seccomp.security.alpha.kubernetes.io/pod: runtime/default ### klusterlet-xxx pod annotations metadata: annotations: k8s.ovn.org/pod-networks: '{"default":{"ip_addresses":["10.128.0.94/23"],"mac_address":"0a:58:0a:80:00:5e","gateway_ips":["10.128.0.1"],"ip_address":"10.128.0.94/23","gateway_ip":"10.128.0.1"}}' k8s.v1.cni.cncf.io/network-status: |- [{ "name": "ovn-kubernetes", "interface": "eth0", "ips": [ "10.128.0.94" ], "mac": "0a:58:0a:80:00:5e", "default": true, "dns": {} }] openshift.io/scc: restricted-v2 seccomp.security.alpha.kubernetes.io/pod: runtime/default workload.openshift.io/warning: skip pod CPUs requests modifications because pod container has both CPU limit and request ### Automation test result SNO management workload partitioning should have management pods pinned to reserved cpus Test result END STEP: Checking cpuset for all running containers via crictl inspect on container host - /home/kni/dgonyier/cnf-gotests/test/ran/workloadpartitioning/tests/workload_partitioning.go:85 @ 04/10/23 15:26:51.378 (973ms) [FAILED] Expected <[]ranwphelper.ContainerInfo | len:4, cap:4>: [ { Name: "addon-agent", Cpus: "2-55,58-111", Namespace: "open-cluster-management-agent-addon", PodName: "cluster-proxy-proxy-agent-84cc68858c-lxg66", Shares: 2, Pid: 1890880, }, { Name: "proxy-agent", Cpus: "2-55,58-111", Namespace: "open-cluster-management-agent-addon", PodName: "cluster-proxy-proxy-agent-84cc68858c-lxg66", Shares: 2, Pid: 1890492, }, { Name: "klusterlet", Cpus: "2-55,58-111", Namespace: "open-cluster-management-agent", PodName: "klusterlet-7bf7dd5b55-k2wxx", Shares: 51, Pid: 22356, }, ] to be empty
- clones
-
OCPBUGS-7906 hostpath and node-driver-registrar containers are not pinned to mgmt cores - no WLP annotation
- Closed
- relates to
-
ACM-4919 klusterlet containers are not pinned to mgmt cores - no WLP annotation
- Closed
-
OCPBUGS-7652 cluster-proxy-service-proxy pod is not pinned to mgmt cores - no WLP annotation
- Closed
- links to
-
RHBA-2023:6257 OpenShift Container Platform 4.13.z bug fix update