Bug 1946591 - Performance Topology Manager test is failing when running cnf-tests in discovery mode
Summary: Performance Topology Manager test is failing when running cnf-tests in discov...
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: Swati Sehgal
QA Contact: Nikita
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-06 13:15 UTC by Sabina Aledort
Modified: 2021-04-08 12:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-08 12:10:35 UTC
Target Upstream Version:
Embargoed:


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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1946584 1 high CLOSED Machine-config controller fails to generate MC, when machine config pool with dashes in name presents under the cluster 2021-09-28 15:48:46 UTC

Description Sabina Aledort 2021-04-06 13:15:57 UTC
Created attachment 1769566 [details]
functests-cn-ran-du.log

Description of problem:
Performance Topology Manager test 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.246 seconds]
[rfe_id:27350][performance]Topology Manager
/remote-source/app/vendor/github.com/openshift-kni/performance-addon-operators/functests/1_performance/topology_manager.go:17
  [test_id:26932][crit:high][vendor:cnf-qe][level:acceptance] should be enabled with the policy specified in profile [It]
  /remote-source/app/vendor/github.com/openshift-kni/performance-addon-operators/functests/1_performance/topology_manager.go:36

  Topology Manager policy mismatch got "" expected "restricted"
  Expected
      <string>: 
  to equal
      <string>: restricted

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

Expected results:
The test should pass.

Comment 1 Sabina Aledort 2021-04-06 13:16:45 UTC
Created attachment 1769567 [details]
tests-artifacts

Comment 2 Martin Sivák 2021-04-08 08:59:27 UTC
I believe this is related to bug 1946584

Comment 3 Martin Sivák 2021-04-08 09:01:23 UTC
Also, undefined Topology Manager policy seems to point to an issue while applying the KubeletConfig.

Swati: check MCO labels and KubeletConfig / PerfProfile MCO selector here please.

Comment 4 Sabina Aledort 2021-04-08 11:43:29 UTC
Created attachment 1770214 [details]
PAO must gather

Comment 5 Swati Sehgal 2021-04-08 12:10:02 UTC
Yep, same issue as https://bugzilla.redhat.com/show_bug.cgi?id=1946584
There are three worker nodes in the cluster
cnfdd5 - with labels node-role.kubernetes.io/worker: "" and node-role.kubernetes.io/worker-cnf: ""
cnfdd6 - with labels node-role.kubernetes.io/worker: "" and node-role.kubernetes.io/worker-cnf: ""
cnfdd7 - with labels node-role.kubernetes.io/worker: "" and node-role.kubernetes.io/worker-duprofile: ""

2 performance profiles 
perf-example.yaml with nodeSelector as node-role.kubernetes.io/worker-duprofile: ""
performance.yaml with nodeSelector as node-role.kubernetes.io/worker-cnf: ""

Which means that cnfdd7 should be targeted and profile should be applied to it.

Comment 6 Swati Sehgal 2021-04-08 12:10:35 UTC

*** 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.