Description of problem (please be detailed as possible and provide log snippests): When installing odf-lvm-operator controller-manager failed to get to running state with the following error: openshift-storage 79s Warning Failed pod/controller-manager-5ff6b7cff8-dlx6x Error: container create failed: time="2022-01-25T13:52:28Z" level=error msg="runc create failed: unable to start container process: exec: \"/metricsexporter\": stat /metricsexporter: no such file or directory" Version of all relevant components (if applicable): 4.10 ocp Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Can't install odf-lvm-operator Is there any workaround available to the best of your knowledge? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? No If this is a regression, please provide more details to justify this: No Steps to Reproduce: 1. Install ocp4.10 2. install ocs catalogesource. 3. Create namespace+operator group+subscription for odf-lvm-operator Actual results: operator is not installing with the following error: openshift-storage 79s Warning Failed pod/controller-manager-5ff6b7cff8-dlx6x Error: container create failed: time="2022-01-25T13:52:28Z" level=error msg="runc create failed: unable to start container process: exec: \"/metricsexporter\": stat /metricsexporter: no such file or directory" Expected results: Operator should be installed with all the components Additional info:
oc get pods -n openshift-storage NAME READY STATUS RESTARTS AGE controller-manager-bdf449886-mm9h4 3/3 Running 0 55s
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.10.0 enhancement, security & bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:1372