Bug 1989536
| Summary: | Pods created by latency tests should request available resources at the moment and/or allows the user to specify the amount | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Talor Itzhak <titzhak> |
| Component: | CNF Platform Validation | Assignee: | Talor Itzhak <titzhak> |
| Status: | CLOSED ERRATA | QA Contact: | Shereen Haj Makhoul <shajmakh> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.8 | CC: | alukiano, aos-bugs, grajaiya, mcornea, shajmakh |
| Target Milestone: | --- | ||
| Target Release: | 4.7.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
The latency test pod was configured to always ask for the total amount of isolated CPUs minus one.
Consequence:
This behavior is not suited for all users.
Fix:
Allow specifying the number of isolated CPUs via the LATENCY_TEST_CPUS environment variable.
Result:
The users will be able to control the number of isolated CPUs and thus have better control over the latency test pod behavior.
|
Story Points: | --- |
| Clone Of: | 1989531 | Environment: | |
| Last Closed: | 2022-02-21 10:19:48 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: | 1989531 | ||
| Bug Blocks: | |||
|
Description
Talor Itzhak
2021-08-03 12:14:15 UTC
verification:
Version:
cnf-tests: cnf-tests-container-v4.7.9-5
pao: registry.redhat.io/openshift4/performance-addon-rhel8-operator@sha256:3985bf8855808bfc6bd48527b9b9337530aaed84dc6aa439c689f498f1f64733
Steps:
podman run -v $(pwd)/:/kubeconfig:Z -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAGE_REGISTRY=registry-proxy.engineering.redhat.com/rh-osbs/ -e CNF_TESTS_IMAGE=openshift4-cnf-tests:v4.7.9-5 -e LATENCY_TEST_RUN=true -e DISCOVERY_MODE=true -e ROLE_WORKER_CNF=worker-cnf -e LATENCY_TEST_CPUS=7 -e LATENCY_TEST_RUNTIME=100 -e MAXIMUM_LATENCY=20 registry-proxy.engineering.redhat.com/rh-osbs/openshift4-cnf-tests:v4.7.9-5 /usr/bin/test-run.sh -ginkgo.v -ginkgo.focus="oslat"
output of pod description:
..
Limits:
cpu: 7
memory: 1Gi
Requests:
cpu: 7
memory: 1Gi
& when not specifying the cpus, it will consume all isolated spus:
Limits:
cpu: 2
memory: 1Gi
Requests:
cpu: 2
memory: 1Gi
when this PP is applied:
apiVersion: performance.openshift.io/v2
kind: PerformanceProfile
metadata:
name: performance
spec:
cpu:
isolated: "3-5"
reserved: "0-2"
realTimeKernel:
enabled: true
nodeSelector:
node-role.kubernetes.io/worker-cnf: ""
Verified successfully.
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.7.43 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:0552 |