Upgrading from OCP 4.16.44 to 4.17.39 with PerformanceProfile and Node tuning enabled leads to Nodes stuck in NoteReatdy,SchedulingDisabled

Issue

• When updating an OCP cluster with PerformanceProfile and Node tuning enabled from 4.16.44 to 4.17.39 or from 4.17.37 to 4.18.24 some nodes may never come back as Ready but are stuck in NotReady,SchedulingDisabled and upgrade is blocked
• kubelet-dependencies.target: Job kubelet-dependencies.target/start failed with result 'dependency'.
  • ocp-tuned-one-shot.service: Failed with result 'exit-code'
Error: crun: creating `/var/lib/ocp-tuned`: openat2 `var/lib/ocp-tuned`: No such file or directory: OCI runtime attempted to invoke a command that was not found