Removing Twistlock Defender from Red Hat OpenShift Container Platform leads many pods to be inaccessible from the console terminal

Issue

• After removing Twistlock Defender from RHOCP, trying to run a container using the RHOCP Console's terminal results in an error:

  ERRO[0000] exec failed: unable to start container process: error starting setns process: fork/exec /proc/self/exe: no such file or directory 
  command terminated with non-zero exit code: exit status 255
  The terminal connection has closed.