Bug 2077067

Summary: [OCP 4.8] Multipath enable at install time on IPI baremetal install
Product: OpenShift Container Platform Reporter: Mario Abajo <mabajodu>
Component: InstallerAssignee: Riccardo Pittau <rpittau>
Installer sub component: OpenShift on Bare Metal IPI QA Contact: Amit Ugol <augol>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: medium CC: eglottma, rpittau
Version: 4.8Keywords: Triaged
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-29 10:06:42 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 Mario Abajo 2022-04-20 15:31:10 UTC
Thanks for opening a bug report!
Before hitting the button, please fill in as much of the template below as you can.
If you leave out information, it's harder to help you.
Be ready for follow-up questions, and please respond in a timely manner.
If we can't reproduce a bug we might close your issue.
If we're wrong, PLEASE feel free to reopen it and explain why.

Version:

$ openshift-install version
"OpenShift Installer 4.8.29-assembly.art3875"
"Built from commit aaa978bb5d76472df23f6e90293e68aaa43a8457"

Platform:

Baremetal

Please specify:
IPI

What happened?

Need to clarify if multipath can be used at installation time in a baremetal IPI installation. With UPI we have documented ways to achieve that but there is no clarification with IPI. If it is not possible, then is it any way to enable it? for example like adding a manifest at installation time that can add a machineConfig with extra kernel parameter "rd.multipath=default" or so.

What did you expect to happen?

Baremetal IPI installation with multipath supported at installation time.

Comment 4 Riccardo Pittau 2022-04-29 10:06:42 UTC

*** This bug has been marked as a duplicate of bug 2070519 ***