Bug 2091944
| Summary: | [4.10] low-latency-hooks.sh script requires ip binary in container image | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yanir Quinn <yquinn> |
| Component: | Performance Addon Operator | Assignee: | Yanir Quinn <yquinn> |
| Status: | CLOSED ERRATA | QA Contact: | Gowrishankar Rajaiyan <grajaiya> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.10 | CC: | browsell, bzvonar, grajaiya, shajmakh |
| Target Milestone: | --- | ||
| Target Release: | 4.10.z | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 2083428 | Environment: | |
| Last Closed: | 2022-07-07 15:57:43 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2083428 | ||
| Bug Blocks: | 2100524 | ||
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.10.21 low-latency extras update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:5484 |
Verification: OCP: 4.10.21 PAO: 4.10.5-1 Steps: apply the following profile: =============================== apiVersion: performance.openshift.io/v2 kind: PerformanceProfile metadata: name: performance spec: cpu: isolated: "0-2" reserved: "3" realTimeKernel: enabled: true nodeSelector: node-role.kubernetes.io/worker-cnf: "" =============================== after applying the profile, CPU mask is 8: from inside a worker-cnf node: cd /sys/devices/virtual/net sh-4.4# find . -name rps_cpus -printf '%p\n' -exec cat {} \; ./ovs-system/queues/rx-0/rps_cpus 008 ./ovn-k8s-mp0/queues/rx-0/rps_cpus 008 ./lo/queues/rx-0/rps_cpus 008 ./c4d1d4cf1105495/queues/rx-0/rps_cpus 008 ./f64eb5cf72a6164/queues/rx-0/rps_cpus 008 ./br-int/queues/rx-0/rps_cpus 008 ./d6f57fc0728d86a/queues/rx-0/rps_cpus 008 ./1f52a12eeaa39bb/queues/rx-0/rps_cpus 008 ./br-ex/queues/rx-0/rps_cpus 008 ./genev_sys_6081/queues/rx-0/rps_cpus 008 after applying the profile there were no errors in the journalctl and same after creating a gu pod: apiVersion: v1 kind: Pod metadata: name: test-runtime annotations: irq-load-balancing.crio.io: "disable" cpu-quota.crio.io: "disable" spec: containers: - name: ubi-minimal-test image: quay.io/yanirq/test-ubi #command: ["sleep", "1h"] resources: requests: cpu: 2 memory: "200M" limits: cpu: 2 memory: "200M" nodeSelector: node-role.kubernetes.io/worker-cnf: "" runtimeClassName: performance-performance from inside a worker-cnf node that the pod was scheduled on: sh-4.4# journalctl --no-pager | grep low-latency-hooks sh-4.4# journalctl | grep "ip: command not found" sh-4.4# moving to verified.