Description of problem:
One of the nmstate handlers is not ready, after aplying  nmstate CR a first time

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

4.15.rc-5

How reproducible:

50%

Steps to Reproduce:
1. Apply the nmstate Custom Resource (CR) for the first time on a cluster
2.
3.
Actual results:

nmstate-handler-7f9hj 0/1 Running 0 4m1s

Feb 07 19:11:24 master-0 kubenswrapper[4052]: I0207 19:11:24.167882 4052 prober.go:107] "Probe failed" probeType="Readiness" pod="openshift-nmstate/nmstate-handler-7f9hj" podUID="d9d0ddcf-bbab-4e71-a9a0-afabb396b8bf" containerName="nmstate-handler" probeResult="failure" output=< Feb 07 19:11:24 master-0 kubenswrapper[4052]: cat: /tmp/healthy: No such file or directory Feb 07 19:11:24 master-0 kubenswrapper[4052]: >

Expected results:

All nmstate hadlers  are up and running

Additional info:
After reinstalling nmstate CR everything works fine.