$ oc get clusterversion
NAME      VERSION                        AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.ci-2020-10-07-024327   True        False         26m     Cluster version is 4.7.0-0.ci-2020-10-07-024327

$ oc project openshift-cluster-node-tuning-operator
Now using project "openshift-cluster-node-tuning-operator" on server "https://api.jmencak.gcp.devcluster.openshift.com:6443".

$ oc get po
NAME                                          READY   STATUS    RESTARTS   AGE
cluster-node-tuning-operator-c957d975-lhfbv   1/1     Running   0          63m
tuned-94zgh                                   1/1     Running   0          50m
tuned-fd9jm                                   1/1     Running   0          56m
tuned-j4m6r                                   1/1     Running   0          56m
tuned-kkxcf                                   1/1     Running   0          56m
tuned-xw9nm                                   1/1     Running   0          50m

$ oc rsh tuned-94zgh 
sh-4.4# rpm -qa|grep tuned
sh-4.4#

Verified on 4.7.0-0.nightly-2020-10-15-051208

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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement 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/RHSA-2020:5633