Bug 1796633 - Node Tuning Operator does not ship with realtime profile
Summary: Node Tuning Operator does not ship with realtime profile
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node Tuning Operator
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.4.0
Assignee: Jiří Mencák
QA Contact: Simon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-30 19:47 UTC by Jiří Mencák
Modified: 2020-05-04 11:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-04 11:28:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-node-tuning-operator pull 111 0 None closed Adding preliminary realtime profile support. 2020-06-16 14:59:35 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-04 11:28:48 UTC

Description Jiří Mencák 2020-01-30 19:47:02 UTC 
Description of problem:
Node Tuning Operator operands do not ship the realtime profile.

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

How reproducible:
Always

Steps to Reproduce:
1. enter a tuned pod
2. ls /usr/lib/tuned/realtime/

Actual results:
No output.

Expected results:
sh-4.2# ls /usr/lib/tuned/realtime/
script.sh  tuned.conf


Additional info:
Comment 1 Jiří Mencák 2020-02-07 08:53:06 UTC 
Fixed in 4.4.0-0.nightly-2020-02-07-030907

$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version             False       True          67m     Unable to apply 4.4.0-0.nightly-2020-02-07-030907: the cluster operator monitoring has not yet successfully rolled out
$ oc project openshift-cluster-node-tuning-operator
Already on project "openshift-cluster-node-tuning-operator" on server "https://api.jm20200207.perf-testing.devcluster.openshift.com:6443".
$ oc get pods
NAME                                         READY   STATUS    RESTARTS   AGE
cluster-node-tuning-operator-959d6b6-2zc5w   1/1     Running   0          67m
tuned-5qk4n                                  1/1     Running   0          57m
tuned-l9c8f                                  1/1     Running   0          49m
tuned-mcks2                                  1/1     Running   0          49m
tuned-qt2cf                                  1/1     Running   0          57m
tuned-xrrqr                                  1/1     Running   0          57m
$ oc rsh tuned-5qk4n 
sh-4.2#  ls /usr/lib/tuned/realtime/
script.sh  tuned.conf
sh-4.2#
Comment 2 Simon 2020-02-18 14:31:52 UTC 
Retest positive!


oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.4.0-0.nightly-2020-02-16-221315   True        False         22h     Cluster version is 4.4.0-0.nightly-2020-02-16-221315

oc get pods -n openshift-cluster-node-tuning-operator 
NAME                                            READY   STATUS    RESTARTS   AGE
cluster-node-tuning-operator-7cf845967c-vt4sn   1/1     Running   0          23h
tuned-4h55x                                     1/1     Running   0          22h
tuned-l42bm                                     1/1     Running   0          23h
tuned-nrzzg                                     1/1     Running   0          22h
tuned-qzldl                                     1/1     Running   0          23h
tuned-rl8fj                                     1/1     Running   0          23h
tuned-xhgxv                                     1/1     Running   0          22h

oc -n openshift-cluster-node-tuning-operator rsh tuned-4h55x

sh-4.2# ls /usr/lib/tuned/realtime/
script.sh  tuned.conf
Comment 5 errata-xmlrpc 2020-05-04 11:28:24 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, 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:0581
Note You need to log in before you can comment on or make changes to this bug.