Bug 2143269 - update ibm csv version to 1.3 for odf 4.12
Summary: update ibm csv version to 1.3 for odf 4.12
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-operator
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.12.0
Assignee: Nitin Goyal
QA Contact: Martin Bukatovic
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-16 13:39 UTC by Nitin Goyal
Modified: 2023-08-09 17:00 UTC (History)
4 users (show)

Fixed In Version: 4.12.0-114
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-02-08 14:06:28 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-operator pull 272 0 None open update ibm operator version to 1.3.0 2022-11-16 13:40:09 UTC
Github red-hat-storage odf-operator pull 276 0 None open Bug 2143269:[release-4.12] update ibm operator version to 1.3.0 2022-11-16 14:40:15 UTC

Description Nitin Goyal 2022-11-16 13:39:02 UTC
Description of problem (please be detailed as possible and provide log
snippests):


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 3 Vered Berenstein Paz 2022-11-22 12:30:06 UTC
The fix has been tested and verified successfully. 
Was able to install ODF-FS plugin successfully on latest ODF build - quay.io/rhceph-dev/odf4-odf-compose-operator-bundle-index:v4.12-v4.12.0-114


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