Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2020931

Summary: cyclictest run missing -m argument
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: CNF Platform ValidationAssignee: Martin Sivák <msivak>
Status: CLOSED ERRATA QA Contact: Nikita <nkononov>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.9CC: aos-bugs, shajmakh, titzhak
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-02-09 19:43:56 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: 2009660    
Bug Blocks:    

Description OpenShift BugZilla Robot 2021-11-07 13:26:23 UTC
+++ This bug was initially created as a clone of Bug #2009660 +++

Description of problem:

Currently when running cyclictest we are not passing -m argument which is important to prevent memory from getting paged out.

Version-Release number of selected component (if applicable):
                "vcs-ref": "b46a47f7c4d3007b8150551c771cc8460fba9dfa",
                "vcs-type": "git",
                "vcs-url": "https://github.com/openshift-kni/cnf-features-deploy",


How reproducible:
100%

Steps to Reproduce:
podman run --name cnf-container-tests  \
  --net=host  \
  -v /home/kni/cnf_tests_mcornea:/kubeconfig:Z  \
  -e KUBECONFIG=/kubeconfig/kubeconfig \
  -e IMAGE_REGISTRY=registry.kni-qe-0.lab.eng.rdu2.redhat.com:5000/ \
  -e CNF_TESTS_IMAGE=cnf-tests \
  -e LATENCY_TEST_RUN=true \
  -e LATENCY_TEST_RUNTIME=3600 \
  -e LATENCY_TEST_CPUS=16 \
  -e OSLAT_MAXIMUM_LATENCY=10 \
  -e CYCLICTEST_MAXIMUM_LATENCY=20 \
  -e HWLATDETECT_MAXIMUM_LATENCY=10 \
  -e ROLE_WORKER_CNF=master \
  -e PERF_TEST_PROFILE=openshift-node-performance-profile \
  -e DISCOVERY_MODE=true \
  quay.io/openshift-kni/cnf-tests \
  /usr/bin/test-run.sh  \
  -ginkgo.focus="\[performance\]\[config\]|\[performance\]\ Latency\ Test\ with\ the\ cyclictest" \
  --junit /junit -ginkgo.v


Actual results:

running the cyclictest command with arguments [-D 3600 -p 1 -t 16 -a 2-9,26-33 -h 30 -i 1000 --quiet]

Expected results:
-m argument passed to cyclictest command

Additional info:

Comment 3 Shereen Haj Makhoul 2022-02-08 13:55:32 UTC
Verification:

Version: 
ocp: 4.9.19
POA: 4.9.5 (image hash d791b343b5b16e94f4fdc0d0585e7843c1aa9d6e140526fda1911078baf6aec5, corresponds to performance-addon-operator-container-v4.9.5-3)
cnf-test image: cnf-tests-container-v4.9.5-5

Run podman focusing on latency tools:

podman run --net=host -v /home/kni/clusterconfigs/auth:/kubeconfig:Z -e KUBECONFIG=/kubeconfig/kubeconfig -e IMAGE_REGISTRY=registry-proxy.engineering.redhat.com/rh-osbs/ -e CNF_TESTS_IMAGE=openshift4-cnf-tests:v4.9.5-5  -e LATENCY_TEST_RUN=true -e LATENCY_TEST_RUNTIME=5 -e LATENCY_TEST_CPUS=2 -e OSLAT_MAXIMUM_LATENCY=3000 -e LATENCY_TEST_DELAY=65 -e CYCLICTEST_MAXIMUM_LATENCY=5200 -e HWLATDETECT_MAXIMUM_LATENCY=5300 -e ROLE_WORKER_CNF=worker-cnf -e PERF_TEST_PROFILE=performance -e DISCOVERY_MODE=true registry-proxy.engineering.redhat.com/rh-osbs/openshift4-cnf-tests:v4.9.5-5 /usr/bin/test-run.sh -ginkgo.focus="\[performance\]\ Latency\ Test" -ginkgo.v 

Result:

Running on machine: cyclictest-fw4sg
Binary: Built with gc go1.16.6 for linux/amd64
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0208 13:32:50.893511       1 node.go:37] Environment information: /proc/cmdline: BOOT_IMAGE=(hd1,gpt3)/ostree/rhcos-56fabc639a679b757ebae30e5f01b2ebd38e9fde9ecae91c41be41d3e89b37f8/vmlinuz-4.18.0-305.34.2.rt7.107.el8_4.x86_64 ip=dhcp random.trust_cpu=on console=tty0 console=ttyS0,115200n8 ostree=/ostree/boot.1/rhcos/56fabc639a679b757ebae30e5f01b2ebd38e9fde9ecae91c41be41d3e89b37f8/0 ignition.platform.id=openstack root=UUID=76fa644f-016b-4160-a091-bba2ccece674 rw rootflags=prjquota skew_tick=1 nohz=on rcu_nocbs=3-5 tuned.non_isolcpus=0000ffff,ffffffff,ffffffc7 intel_pstate=disable nosoftlockup tsc=nowatchdog intel_iommu=on iommu=pt isolcpus=managed_irq,3-5 systemd.cpu_affinity=0,1,2,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79 + +
I0208 13:32:50.893709       1 node.go:44] Environment information: kernel version 4.18.0-305.34.2.rt7.107.el8_4.x86_64
I0208 13:33:55.894523       1 main.go:51] running the cyclictest command with arguments [-D 5 -p 95 -t 2 -a 3,43 -h 30 -i 1000 --mlockall --quiet]
I0208 13:34:00.959314       1 main.go:57] succeeded to run the cyclictest command: # /dev/cpu_dma_latency set to 0us
# Histogram
000000 000000	000000
000001 000000	000000
000002 004695	004615

According to the above output, --mlockall is now passed to the cyclictest to prevent memory allocation from paging out.

Comment 5 errata-xmlrpc 2022-02-09 19:43:56 UTC
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.9.19 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:0471