Bug 2321043 - Local storage operator image not found for ppc64le in OCP 4.12
Summary: Local storage operator image not found for ppc64le in OCP 4.12
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: build
Version: 4.12
Hardware: ppc64le
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Tamil
QA Contact: Petr Balogh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-22 16:36 UTC by narayanspg
Modified: 2024-10-28 08:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OCSBZM-9418 0 None None None 2024-10-22 16:39:04 UTC

Description narayanspg 2024-10-22 16:36:25 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
While deploying ODF 4.12.14 we tried to install LSO(4.12.0-202410010030) but the operator installation is failing with image not found error for ppc64le.


Version of all relevant components (if applicable):
LSO 4.12.0-202410010030
OCP 4.12.61

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

Is there any workaround available to the best of your knowledge?
Yes 4.13 LSO is used as workaround.

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?
Yes

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


Steps to Reproduce:
1. Deploy OCP 4.12 latest on IBM Power
2. install LSO 
3. lso installation fails


Actual results:
  Local storage operator not installing

Expected results:
 Local storage operator should install.

Additional info:
Note You need to log in before you can comment on or make changes to this bug.