Bug 2193234
| Summary: | [DPDK checkup] Node selection from ConfigMap not applied | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Yossi Segev <ysegev> | ||||
| Component: | Networking | Assignee: | Petr Horáček <phoracek> | ||||
| Status: | ON_QA --- | QA Contact: | Nir Rozen <nrozen> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.13.0 | CC: | omisan | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.14.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | v4.14.0.rhel9-1146 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
*** Bug 2193235 has been marked as a duplicate of this bug. *** |
Created attachment 1962335 [details] DPDK checkup manifests Description of problem: When running a DPDK checkup job, attempting to run the VM and the traffic generator on specific nodes is ignored. Version-Release number of selected component (if applicable): CNV 4.13.0 container-native-virtualization-kubevirt-dpdk-checkup-rhel9:v4.13.0-37 How reproducible: 100% Steps to Reproduce: 1. Create namespace for the job, and change context to the new namespace. $ oc create ns dpdk-checkup-ns $ oc project dpdk-checkup-ns 2. Label the worker nodes with "worker-dpdk" label. 3. Apply the resources manifests in the attached file in their numeric order: $ oc apply -f 1-dpdk-checkup-resources.yaml $ oc apply -f 2-dpdk-checkup-scc.yaml ... change the resources according to your cluster. In the ConfigMap manifest - note these 2 params: spec.param.trafficGeneratorNodeSelector: "cnv-qe-infra-12.cnvqe2.lab.eng.rdu2.redhat.com" spec.param.DPDKLabelSelector: "cnv-qe-infra-12.cnvqe2.lab.eng.rdu2.redhat.com" 4. After applying the job itself (8-dpdk-checkup-job.yaml) - follow the pods that are created and the nodes they are created on (or wait for the job to finish, as this info will also appear in the result ConfigMap). $ oc get cm dpdk-checkup-config -o yaml | grep "status.result" | grep Node status.result.DPDKVMNode: cnv-qe-infra-13.cnvqe2.lab.eng.rdu2.redhat.com status.result.trafficGeneratorNode: cnv-qe-infra-13.cnvqe2.lab.eng.rdu2.redhat.com <BUG> Although the setup ConfigMap is attempting to set cnv-qe-infra-12.cnvqe2.lab.eng.rdu2.redhat.com as the node for both the traffic generator and the VM, the actual used node is cnv-qe-infra-13.cnvqe2.lab.eng.rdu2.redhat.com. Additional info: Checking the log of the checkup job pod shows that these fields remain blank and not taken from the ConfigMap: 2023/05/04 14:05:11 "trafficGeneratorNodeLabelSelector": "" 2023/05/04 14:05:11 "trafficGeneratorPacketsPerSecond": "8m" 2023/05/04 14:05:11 "DPDKNodeLabelSelector": ""