Bug 1896798 - openshift4-cnf-tests | detection of the performance addon operator is not proper handled since it is based in namespace location
Summary: openshift4-cnf-tests | detection of the performance addon operator is not pro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: CNF Platform Validation
Version: 4.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.z
Assignee: Federico Paolinelli
QA Contact: Nikita
URL:
Whiteboard:
Depends On: 1894861
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-11 15:01 UTC by Federico Paolinelli
Modified: 2020-12-17 06:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1894861
Environment:
Last Closed: 2020-12-17 06:55:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift-kni cnf-features-deploy pull 367 0 None closed Bug 1896798: Make it possible to override the namespace used by the operators, plus switch the pao default one. 2020-11-26 12:07:43 UTC
Red Hat Product Errata RHBA-2020:5187 0 None None None 2020-12-17 06:56:03 UTC

Description Federico Paolinelli 2020-11-11 15:01:14 UTC
+++ This bug was initially created as a clone of Bug #1894861 +++

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 Nikita 2020-11-23 15:02:42 UTC
Verified with openshift4-cnf-tests:v4.6.0-31 on top of OCP 4.6.5 looks good.

Comment 4 errata-xmlrpc 2020-12-17 06:55: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.6.8 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-2020:5187


Note You need to log in before you can comment on or make changes to this bug.