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

Bug 1894861

Summary:	openshift4-cnf-tests \| detection of the performance addon operator is not proper handled since it is based in namespace location
Product:	OpenShift Container Platform	Reporter:	Alberto Losada <alosadag>
Component:	CNF Platform Validation	Assignee:	Federico Paolinelli <fpaoline>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikita <nkononov>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.6	CC:	elevin
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1896798 (view as bug list)		Environment:
Last Closed:	2022-08-24 12:52:49 UTC	Type:	Bug
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:
Bug Blocks:	1896798

Description Alberto Losada 2020-11-05 10:00:35 UTC

Description of problem:

Verification of the installation of the Performance Addon Operator (PAO) is done by checking that the operator is running in the openshift-performance-addon namespace.

As per documentation, the suggested namespace for installing Performance Addon Operator is openshift-performance-addon-operator in release 4.6. https://docs.openshift.com/container-platform/4.6/scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.html#install-operator-cli_cnf-master

However, it is possible to let the user install it in a different namespace.


Version-Release number of selected component (if applicable):

PAO 4.6
OCP 4.6.1

How reproducible:

Follow the official documentation to install the PAO from CLI (https://docs.openshift.com/container-platform/4.6/scalability_and_performance/cnf-performance-addon-operator-for-low-latency-nodes.html#install-operator-cli_cnf-master)


Actual results:

When running cnf-tests, it returns an error because PAO is not running in the "expected cnf-test" namespace.

$ podman run -v $(pwd)/:/kubeconfig:Z -v $(pwd)/reports:/reports:Z -e KUBECONFIG=/kubeconfig/kubeconfig -e DISCOVERY_MODE=true -e CNF_TESTS_IMAGE=cnf-tests-rhel8:4.6 -e DPDK_TESTS_IMAGE=dpdk-base-rhel8:4.6 registry.redhat.io/openshift4/cnf-tests-rhel8:4.6 /usr/bin/test-run.sh -ginkgo.focus="performance"

running /usr/bin/validationsuite -ginkgo.focus=performance
I1104 15:08:27.009776       8 request.go:621] Throttling request took 1.048365068s, request: GET:https://api.cnf10.kni.lab.eng.bos.redhat.com:6443/apis/authentication.k8s.io/v1?timeout=32s
Running Suite: CNF Features e2e validation
==========================================
Random Seed: 1604502504
Will run 3 of 17 specs
SSS
------------------------------
• Failure [0.168 seconds]
validation
/remote-source/app/validationsuite/cluster/validation.go:39
  performance
  /remote-source/app/validationsuite/cluster/validation.go:78
    should have the performance operator namespace [It]


Expected results:

cnf-test suite should detect the operator properly and execute the tests.

Additional info:

Comment 1 elevin 2020-11-19 12:07:25 UTC

!Verified with "openshift-performance-addon-operator" namespace and via variable PERFORMANCE_OPERATOR_NAMESPACE

Client Version: 4.6.0-202005061824-29e9a33
Server Version: 4.6.4
Kubernetes Version: v1.19.0+9f84db3
Container version: registry-proxy.engineering.redhat.com/rh-osbs/openshift4-cnf-tests:rhaos-4.7-rhel-8-containers-candidate-75374-20201113174236
NameSpace: openshift-performance-addon-operator

---------------------------------------------------------------------------------------------------------------------------------------------------

running /usr/bin/validationsuite --report /report -ginkgo.v -ginkgo.focus=performance
I1119 11:07:09.550830       6 request.go:621] Throttling request took 1.027448406s, request: GET:https://api.cluster2.savanna.lab.eng.rdu2.redhat.com:6443/apis/packages.operators.coreos.com/v1?timeout=32s
Failed to find profile in discovery mode no matches for kind "PerformanceProfile" in version "performance.openshift.io/v2"
Running Suite: CNF Features e2e validation
==========================================
Random Seed: 1605784028
Will run 3 of 17 specs

SSS
------------------------------
validation performance 
  should have the performance operator namespace
  /remote-source/app/validationsuite/cluster/validation.go:80
•
------------------------------
validation performance 
  should have the performance operator deployment in running state
  /remote-source/app/validationsuite/cluster/validation.go:85
•
------------------------------
validation performance 
  Should have the performance CRD available in the cluster
  /remote-source/app/validationsuite/cluster/validation.go:98
•SSSSSSSSSSS
Ran 3 of 17 Specs in 0.029 seconds
SUCCESS! -- 3 Passed | 0 Failed | 0 Pending | 14 Skipped
PASS

Comment 3 Carlos Goncalves 2022-08-24 12:52:49 UTC

Bulk closing of all "CNF Platform Validation" component BZs assigned to CNF Network team members and in VERIFIED status for longer than 1 month.