-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.13, 4.12.z, 4.11.z, 4.10.z
-
Moderate
-
No
-
CNF RAN Sprint 233, CNF RAN Sprint 234, CNF RAN Sprint 235, CNF RAN Sprint 236
-
4
-
False
-
-
-
Description of problem:
cluster-proxy-service-proxy pod under open-cluster-management-agent-addon is not pinned to reserved management cores. It is not annotated with target.workload.openshift.io/management: '{"effect":"PreferredDuringScheduling"}'
Version-Release number of selected component (if applicable):
4.11.28, 4.10.52, 4.13
How reproducible:
Always
Steps to Reproduce:
1. Deploy SNO via ZTP with workload partitioning enabled 2. Check mgmt pods affinity 3.
Actual results:
cluster-proxy-service-proxy pod under open-cluster-management-agent-addon does not have workload partitioning annotation, and it is 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:
Pod annotation: metadata: annotations: k8s.ovn.org/pod-networks: '{"default":{"ip_addresses":["fd01:0:0:1::5e/64"],"mac_address":"0a:58:2c:12:76:19","gateway_ips":["fd01:0:0:1::1"],"ip_address":"fd01:0:0:1::5e/64","gateway_ip":"fd01:0:0:1::1"}}' k8s.v1.cni.cncf.io/network-status: |- [{ "name": "ovn-kubernetes", "interface": "eth0", "ips": [ "fd01:0:0:1::5e" ], "mac": "0a:58:2c:12:76:19", "default": true, "dns": {} }] k8s.v1.cni.cncf.io/networks-status: |- [{ "name": "ovn-kubernetes", "interface": "eth0", "ips": [ "fd01:0:0:1::5e" ], "mac": "0a:58:2c:12:76:19", "default": true, "dns": {} }] openshift.io/scc: restricted-v2 seccomp.security.alpha.kubernetes.io/pod: runtime/default creationTimestamp: "2023-02-16T16:31:26Z" generateName: cluster-proxy-service-proxy-5496b4f57b- The pod is pinned to the isolated cpus. /var/lib/jenkins/workspace/ocp-far-edge-vran-deployment/cnf-gotests/test/ran/workloadpartitioning/tests/workload_partitioning.go:113 [FAILED] Expected <[]ranwphelper.ContainerInfo | len:1, cap:1>: [ { Name: "cluster-proxy-service-proxy", Cpus: "2-55,58-111", Namespace: "open-cluster-management-agent-addon", PodName: "cluster-proxy-service-proxy-5496b4f57b-dgrlg", Shares: 2, Pid: 40103, }, ] to be empty
- blocks
-
OCPBUGS-11987 cluster-proxy-service-proxy pod is not pinned to mgmt cores - no WLP annotation
- Closed
-
OCPBUGS-11988 cluster-proxy-service-proxy pod is not pinned to mgmt cores - no WLP annotation
- Closed
- is cloned by
-
OCPBUGS-7906 hostpath and node-driver-registrar containers are not pinned to mgmt cores - no WLP annotation
- Closed
-
OCPBUGS-11987 cluster-proxy-service-proxy pod is not pinned to mgmt cores - no WLP annotation
- Closed
-
OCPBUGS-11988 cluster-proxy-service-proxy pod is not pinned to mgmt cores - no WLP annotation
- Closed
- is related to
-
OCPBUGS-11604 addon-agent, klusterlet, proxy-agent containers are not pinned to mgmt cores - no WLP annotation
- Closed
- links to
-
RHSA-2023:6257 OpenShift Container Platform 4.13.z security update
- mentioned on