Bug 2047562

Summary:	CSI Sidecar containers do not start
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	N Balachandran <nibalach>
Component:	lvm-operator	Assignee:	Leela Venkaiah Gangavarapu <lgangava>
Status:	CLOSED ERRATA	QA Contact:	Shay Rozen <srozen>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	jolmomar, lgangava, muagarwa, nberry, ocs-bugs, odf-bz-bot, rperiyas, sapillai
Target Milestone:	---
Target Release:	ODF 4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.10.0-132	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-13 18:52:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description N Balachandran 2022-01-28 04:47:38 UTC

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:

Comment 5 Shay Rozen 2022-02-01 15:30:26 UTC

Fixed in 4.10.130

Comment 10 errata-xmlrpc 2022-04-13 18:52:21 UTC

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