Bug 1946588 - Performance CPU reservation verification on worker node is failing when running cnf-tests in discovery mode
Summary: Performance CPU reservation verification on worker node is failing when runni...
Keywords:
Status: CLOSED DUPLICATE of bug 1946584
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: CNF Platform Validation
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Artyom
QA Contact: Nikita
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-06 13:05 UTC by Sabina Aledort
Modified: 2021-06-01 13:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-01 13:49:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
functests-cn-ran-du.log (80.48 KB, text/plain)
2021-04-06 13:05 UTC, Sabina Aledort 		no flags Details
tests-artifacts (234.94 KB, application/x-xz)
2021-04-06 13:06 UTC, Sabina Aledort 		no flags Details
PAO must gather (760.09 KB, application/x-xz)
2021-04-08 11:44 UTC, Sabina Aledort 		no flags Details
View All

Description Sabina Aledort 2021-04-06 13:05:27 UTC 
Created attachment 1769561 [details]
functests-cn-ran-du.log

Description of problem:
Performance CPU reservation verification on worker node is failing when running cnf-tests in discovery mode.

Version-Release number of selected component (if applicable):
4.8.0-0.nightly-2021-04-03-092337
CNF tests image: registry-proxy.engineering.redhat.com/rh-osbs/openshift4-cnf-tests:v4.8.0-19

How reproducible:
Run containerised tests in discovery mode against existing 4.8 clusters.

Steps to Reproduce:
Run containerised tests in discovery mode against existing 4.8 clusters for performance addon operator feature:

podman run -v /root/cnf_ci/cnf-internal-deploy/_cache/:/kubeconfig:Z -v /tmp/artifacts/cn-ran-du:/reports:Z -e CLEAN_PERFORMANCE_PROFILE=false -e CNF_TESTS_IMAGE=openshift4-cnf-tests:v4.8.0-19 -e DPDK_TESTS_IMAGE=dpdk-base:v4.8.0-2 -e IMAGE_REGISTRY=registry-proxy.engineering.redhat.com/rh-osbs/ -e KUBECONFIG=/kubeconfig/kubeconfig -e SCTPTEST_HAS_NON_CNF_WORKERS=false -e DISCOVERY_MODE=true -e NODES_SELECTOR=node-role.kubernetes.io/worker-duprofile= -e ROLE_WORKER_CNF=worker-duprofile -e LATENCY_TEST_RUN=false -e LATENCY_TEST_RUNTIME=600 -e OSLAT_MAXIMUM_LATENCY=200 registry-proxy.engineering.redhat.com/rh-osbs/openshift4-cnf-tests:v4.8.0-19 /usr/bin/test-run.sh -ginkgo.focus 'performance|ptp|sriov|sctp|dpdk|ovn' -junit /reports/ -report /reports/

Actual results:
• Failure [0.014 seconds]
[rfe_id:27363][performance] CPU Management
/remote-source/app/vendor/github.com/openshift-kni/performance-addon-operators/functests/1_performance/cpu_management.go:38
  Verification of configuration on the worker node
  /remote-source/app/vendor/github.com/openshift-kni/performance-addon-operators/functests/1_performance/cpu_management.go:74
    [test_id:28528][crit:high][vendor:cnf-qe][level:acceptance] Verify CPU reservation on the node [It]
    /remote-source/app/vendor/github.com/openshift-kni/performance-addon-operators/functests/1_performance/cpu_management.go:75

    Expected
        <int64>: 52
    to equal
        <int64>: 5

    /remote-source/app/vendor/github.com/openshift-kni/performance-addon-operators/functests/1_performance/cpu_management.go:79

Expected results:
The test should pass.
Comment 1 Sabina Aledort 2021-04-06 13:06:16 UTC 
Created attachment 1769563 [details]
tests-artifacts
Comment 2 Sabina Aledort 2021-04-08 11:44:17 UTC 
Created attachment 1770215 [details]
PAO must gather
Comment 3 Artyom 2021-06-01 13:49:29 UTC 
The tests failed because it the MC controller failed to apply the kubeletconfig, see
  - lastHeartbeatTime: "2021-04-07T14:04:40Z"
    lastTransitionTime: "2021-04-07T14:04:40Z"
    message: 'could not get kubelet config key: error converting kubelet to int: strconv.Atoi:
      parsing "kubelet": invalid syntax'

*** This bug has been marked as a duplicate of bug 1946584 ***
Note You need to log in before you can comment on or make changes to this bug.