-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.13
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
node-driver-registrar and hostpath containers in pod shared-resource-csi-driver-node-xxxxx under openshift-cluster-csi-drivers namespace are not pinned to reserved management cores.
Version-Release number of selected component (if applicable):
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:
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:
pod metadata
metadata:
annotations:
k8s.ovn.org/pod-networks: '{"default":{"ip_addresses":["fd01:0:0:1::5f/64"],"mac_address":"0a:58:97:51:ad:31","gateway_ips":["fd01:0:0:1::1"],"ip_address":"fd01:0:0:1::5f/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::5f"
],
"mac": "0a:58:97:51:ad:31",
"default": true,
"dns": {}
}]
k8s.v1.cni.cncf.io/networks-status: |-
[{
"name": "ovn-kubernetes",
"interface": "eth0",
"ips": [
"fd01:0:0:1::5f"
],
"mac": "0a:58:97:51:ad:31",
"default": true,
"dns": {}
}]
openshift.io/scc: privileged
/var/lib/jenkins/workspace/ocp-far-edge-vran-deployment/cnf-gotests/test/ran/workloadpartitioning/tests/workload_partitioning.go:113
SNO management workload partitioning [It] should have management pods pinned to reserved 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:3, cap:4>: [
{
Name: "hostpath",
Cpus: "2-55,58-111",
Namespace: "openshift-cluster-csi-drivers",
PodName: "shared-resource-csi-driver-node-vzvtc",
Shares: 10,
Pid: 41650,
},
{
Name: "cluster-proxy-service-proxy",
Cpus: "2-55,58-111",
Namespace: "open-cluster-management-agent-addon",
PodName: "cluster-proxy-service-proxy-66599b78bf-k2dvr",
Shares: 2,
Pid: 35093,
},
{
Name: "node-driver-registrar",
Cpus: "2-55,58-111",
Namespace: "openshift-cluster-csi-drivers",
PodName: "shared-resource-csi-driver-node-vzvtc",
Shares: 10,
Pid: 34782,
},
]
to be empty
In [It] at: /var/lib/jenkins/workspace/ocp-far-edge-vran-deployment/cnf-gotests/test/ran/workloadpartitioning/ranwphelper/ranwphelper.go:172 @ 02/22/23 01:05:00.268
cluster-proxy-service-proxy is reported in https://issues.redhat.com/browse/OCPBUGS-7652
- blocks
-
OCPBUGS-11432 hostpath and node-driver-registrar containers are not pinned to mgmt cores - no WLP annotation
-
- Closed
-
- clones
-
OCPBUGS-7652 cluster-proxy-service-proxy pod is not pinned to mgmt cores - no WLP annotation
-
- Closed
-
- is cloned by
-
OCPBUGS-11604 addon-agent, klusterlet, proxy-agent containers are not pinned to mgmt cores - no WLP annotation
-
- Closed
-
-
OCPBUGS-8683 CSI driver + operator containers are not pinned to mgmt cores
-
- Closed
-
-
OCPBUGS-11432 hostpath and node-driver-registrar containers are not pinned to mgmt cores - no WLP annotation
-
- Closed
-
- links to
-
RHSA-2023:5006
OpenShift Container Platform 4.14.z security update