Description of problem (please be detailed as possible and provide log
snippests):

The downstream CephCSI containers in the topolvm-controller and topolvm-node pods do not start as the entrypoint for the downstream CSI sidecar images is not the same as that of the upstream images.


https://github.com/kubernetes-csi/livenessprobe/blob/master/Dockerfile:
ENTRYPOINT ["/livenessprobe"]

https://github.com/openshift/csi-livenessprobe/blob/release-4.10/Dockerfile.openshift
ENTRYPOINT ["/usr/bin/livenessprobe"]


Errors:

 Normal   Pulled   23s  kubelet  Successfully pulled image "quay.io/rhceph-dev/openshift-ose-csi-livenessprobe@sha256:550a497f66083c1d3010db376efed35f0a5f522e75db395db00c3e683503c5d1" in 14.421941499s
  Warning  Failed   22s  kubelet  Error: container create failed: time="2022-01-28T04:10:24Z" level=warning msg="cgroup: subsystem does not exist"
time="2022-01-28T04:10:24Z" level=warning msg="cgroup: subsystem does not exist"
time="2022-01-28T04:10:24Z" level=warning msg="cgroup: subsystem does not exist"
time="2022-01-28T04:10:24Z" level=error msg="container_linux.go:380: starting container process caused: exec: \"/livenessprobe\": stat /livenessprobe: no such file or directory"

Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info: