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

Bug 2033225

Summary: The controller does not watch for changes under the tuned profile status
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Performance Addon OperatorAssignee: Artyom <alukiano>
Status: CLOSED ERRATA QA Contact: Gowrishankar Rajaiyan <grajaiya>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.10CC: aos-bugs, shajmakh
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: performance-addon-operator-container-v4.9.4-4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-10 14:42:55 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: 2033224    
Bug Blocks: 2034179    

Description OpenShift BugZilla Robot 2021-12-16 09:38:34 UTC
+++ This bug was initially created as a clone of Bug #2033224 +++

Description of problem:
PAO controller does not watch for changes under the tuned profile status that prevent correct reflection of tuned profile status under the performance profile.

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

How reproducible:
Always

Steps to Reproduce:
1. Run e2e test https://github.com/openshift-kni/performance-addon-operators/blob/3644ec5779580f30962e0cf9c12548a235d6194e/functests/3_performance_status/status.go#L119
2.
3.

Actual results:
The test fails.

Expected results:
The test should pass.

Additional info:

Comment 3 Shereen Haj Makhoul 2021-12-22 20:37:01 UTC
Verification:

PAO build: v4.9.4-6

Run result:
  ------------------------------

[2021-12-22T16:15:57.511Z] Status testing of performance profile [rfe_id:28881][performance] Performance Addons detailed status 

[2021-12-22T16:15:57.511Z]   [test_id:40402] Tuned profile status tied to Performance Profile

[2021-12-22T16:15:57.511Z]   /home/jenkins/workspace/CNF/cnf-compute-4.9/performance-addon-operators/functests/3_performance_status/status.go:119

[2021-12-22T16:15:57.511Z] STEP: Waiting for performance profile condition to be Degraded

[2021-12-22T16:16:28.191Z] STEP: Deleting bad Tuned and waiting when Degraded state is removed

[2021-12-22T16:17:00.334Z] 

[2021-12-22T16:17:00.334Z] • [SLOW TEST:60.047 seconds]

[2021-12-22T16:17:00.334Z] Status testing of performance profile

[2021-12-22T16:17:00.334Z] /home/jenkins/workspace/CNF/cnf-compute-4.9/performance-addon-operators/functests/3_performance_status/status.go:30

[2021-12-22T16:17:00.334Z]   [rfe_id:28881][performance] Performance Addons detailed status

[2021-12-22T16:17:00.334Z]   /home/jenkins/workspace/CNF/cnf-compute-4.9/performance-addon-operators/functests/3_performance_status/status.go:57

[2021-12-22T16:17:00.334Z]     [test_id:40402] Tuned profile status tied to Performance Profile

[2021-12-22T16:17:00.334Z]     /home/jenkins/workspace/CNF/cnf-compute-4.9/performance-addon-operators/functests/3_performance_status/status.go:119

[2021-12-22T16:17:00.334Z] ------------------------------

[2021-12-22T16:17:04.200Z] 

[2021-12-22T16:17:04.200Z] JUnit report was created: /home/jenkins/workspace/CNF/cnf-compute-4.9/artifacts/4.9/unit_report_performance_status.xml

[2021-12-22T16:17:04.200Z] 

[2021-12-22T16:17:04.200Z] Ran 4 of 4 Specs in 156.368 seconds

[2021-12-22T16:17:04.200Z] SUCCESS! -- 4 Passed | 0 Failed | 0 Flaked | 0 Pending | 0 Skipped

[2021-12-22T16:17:04.200Z] PASS

Test passed successfully, hence verified.

Comment 5 errata-xmlrpc 2022-01-10 14:42:55 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.13 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:0046