Bug 2047625

Summary:	Dockerfile changes for topolvm
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	N Balachandran <nibalach>
Component:	lvm-operator	Assignee:	Deepshikha khandelwal <dkhandel>
Status:	CLOSED ERRATA	QA Contact:	Shay Rozen <srozen>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	branto, jolmomar, lgangava, mmuench, muagarwa, nberry, ocs-bugs, odf-bz-bot, 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 07:14:25 UTC

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

The base image for the odf-topolvm image is ubi-minimal which does not contain nsenter. odf-topolvm requires nsenter to run lvm commands on the host.


```Error: fork/exec /usr/bin/nsenter: no such file or directory
fork/exec /usr/bin/nsenter: 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?
Yes. 

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 7 Shay Rozen 2022-02-01 15:29:38 UTC

Fixed in 4.10.130

Comment 12 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