Description of problem:
ssp-operator pods sometimes end-up in CrashLoopBackOff state.
Also VIRT pods are affected (virt-controller and/or virt-operator)

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

How reproducible:
Sporadic. We couldn't find the exact trigger, not all deployed clusters can be affected

Steps to Reproduce:
1.Deploy 4.14 CNV cluster
2.After some time, CNV pods start to fail
3.

Actual results:
openshift-cnv pods are in CrashLoopBackOff state

Expected results:
All CNV pods are in Running state

Additional info:
pods -A | grep -v Running | grep -v Completed
NAMESPACE NAME READY STATUS RESTARTS AGE
openshift-cnv cdi-deployment-844845fd6d-9pkjr 0/1 CrashLoopBackOff 186 (4m24s ago) 16h
openshift-cnv cdi-operator-6499bcc5b7-xxtzc 0/1 CrashLoopBackOff 187 (4m32s ago) 16h
openshift-cnv hostpath-provisioner-operator-f4dc64d86-vhvlf 0/1 CrashLoopBackOff 187 (5m ago) 16h
openshift-cnv ssp-operator-644c98fdc9-cjncw 0/1 CrashLoopBackOff 188 (4m49s ago) 16h
openshift-cnv virt-controller-b5b88dd59-prtk7 0/1 CrashLoopBackOff 186 (84s ago) 16h
openshift-cnv virt-controller-b5b88dd59-wkpvz 0/1 CrashLoopBackOff 187 (81s ago) 16h
openshift-cnv virt-operator-5cb848c66c-2mzmk 0/1 CrashLoopBackOff 181 (2m16s ago) 16h
openshift-cnv virt-operator-5cb848c66c-cnkvh 0/1 CrashLoopBackOff 182 (2m44s ago) 16h