OCP upgrade from 4.12.6 to 4.13 nightly failed due to tuned operator is not available. 


$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.12.7    True        True          155m    Unable to apply 4.13.0-0.nightly-2023-03-13-122248: the cluster operator node-tuning is not available


$ oc get co 
...
node-tuning                                4.13.0-0.nightly-2023-03-13-122248   False       True          False      126m    DaemonSet "tuned" has no available Pod(s)


Following events in Terminating tuned pod: 

$ oc get pods -n openshift-cluster-node-tuning-operator
NAME                                            READY   STATUS        RESTARTS   AGE
cluster-node-tuning-operator-5c458cc9d5-fp9zn   1/1     Running       0          136m
tuned-94tcq                                     0/1     Terminating   2          4h43m

$ oc describe pods -n openshift-cluster-node-tuning-operator tuned-94tcq
...
  Normal   Started            3h6m                 kubelet            Started container tuned
  Normal   Killing            126m                 kubelet            Stopping container tuned
  Warning  FailedPreStopHook  126m                 kubelet            Exec lifecycle hook ([/var/lib/tuned/bin/run stop]) for Container "tuned" in Pod "tuned-94tcq_openshift-cluster-node-tuning-operator(e12b341f-0683-4ccf-870c-bb3d24de073f)" failed - error: command '/var/lib/tuned/bin/run stop' exited with 1: openshift-tuned stop response: 
, message: "openshift-tuned stop response: \n"

4.13

Intermittent

1. Upgrade SNO from OCP 4.12.7 to 4.13 nightly
2.
3.

Upgrade stuck at waiting for node-tuning operator to be available

$ oc get clusterversion NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS version   4.12.7    True        True          155m    Unable to apply 4.13.0-0.nightly-2023-03-13-122248: the cluster operator node-tuning is not available

Upgrade succeed

Workaround: manually reboot DUT