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

Bug 2034179

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 Operator	Assignee:	Artyom <alukiano>
Status:	CLOSED ERRATA	QA Contact:	Gowrishankar Rajaiyan <grajaiya>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	aos-bugs, shajmakh
Target Milestone:	---
Target Release:	4.8.z
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	performance-addon-operator-container-v4.8.5-6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-05 18:55:48 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:	2033225
Bug Blocks:

Description OpenShift BugZilla Robot 2021-12-20 10:33:39 UTC

+++ This bug was initially created as a clone of Bug #2033225 +++

+++ 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 4 Shereen Haj Makhoul 2021-12-29 11:32:24 UTC

Verifiation:
Builds: 
PAO: v4.8.5-6
OCP: 4.8.0-0.nightly-2021-12-23-010813



The result of the test run:
56Z] Status testing of performance profile [rfe_id:28881][performance] Performance Addons detailed status 

[2021-12-29T10:59:11.556Z]   [test_id:40402] Tuned profile status tied to Performance Profile

[2021-12-29T10:59:11.556Z]   /home/jenkins/workspace/CNF/cnf-compute-4.8/performance-addon-operators/functests/3_performance_status/status.go:119

[2021-12-29T10:59:11.556Z] STEP: Waiting for performance profile condition to be Degraded

[2021-12-29T10:59:42.721Z] STEP: Deleting bad Tuned and waiting when Degraded state is removed

[2021-12-29T11:00:09.633Z] 

[2021-12-29T11:00:09.633Z] • [SLOW TEST:60.061 seconds]

[2021-12-29T11:00:09.633Z] Status testing of performance profile

[2021-12-29T11:00:09.633Z] /home/jenkins/workspace/CNF/cnf-compute-4.8/performance-addon-operators/functests/3_performance_status/status.go:30

[2021-12-29T11:00:09.633Z]   [rfe_id:28881][performance] Performance Addons detailed status

[2021-12-29T11:00:09.633Z]   /home/jenkins/workspace/CNF/cnf-compute-4.8/performance-addon-operators/functests/3_performance_status/status.go:57

[2021-12-29T11:00:09.633Z]     [test_id:40402] Tuned profile status tied to Performance Profile

[2021-12-29T11:00:09.633Z]     /home/jenkins/workspace/CNF/cnf-compute-4.8/performance-addon-operators/functests/3_performance_status/status.go:119

[2021-12-29T11:00:09.633Z] ------------------------------

[2021-12-29T11:00:15.654Z] 

[2021-12-29T11:00:15.654Z] JUnit report was created: /home/jenkins/workspace/CNF/cnf-compute-4.8/artifacts/4.8/unit_report_performance_status.xml

[2021-12-29T11:00:15.654Z] 

[2021-12-29T11:00:15.654Z] Ran 4 of 4 Specs in 816.444 seconds

[2021-12-29T11:00:15.654Z] SUCCESS! -- 4 Passed | 0 Failed | 0 Flaked | 0 Pending | 0 Skipped

Test passed successfully, hence verified.

Comment 6 errata-xmlrpc 2022-01-05 18:55:48 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.8.25 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:0036