Bug 2104833 - Need to update configmap for IBM storage odf operator GA
Summary: Need to update configmap for IBM storage odf operator GA
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-operator
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ODF 4.11.0
Assignee: Nitin Goyal
QA Contact: Martin Bukatovic
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-07 09:01 UTC by Tal Yichye
Modified: 2023-08-09 17:00 UTC (History)
7 users (show)

Fixed In Version: 4.11.0-131
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2116950 (view as bug list)
Environment:
Last Closed: 2022-08-24 13:55:09 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-operator pull 229 0 None open update ibm CSV versions 2022-07-07 09:06:51 UTC
Github red-hat-storage odf-operator pull 230 0 None open Bug 2104833: [release-4.11] update ibm CSV versions 2022-07-07 13:40:40 UTC
Red Hat Product Errata RHSA-2022:6156 0 None None None 2022-08-24 13:55:50 UTC

Description Tal Yichye 2022-07-07 09:01:09 UTC
Description of problem (please be detailed as possible and provide log
snippests):

Need to update the following fields for odf-operator before we will publish our new release 1.0.1
IBM_CSI_SUBSCRIPTION_STARTINGCSV: ibm-block-csi-operator.v1.9.0
IBM_SUBSCRIPTION_STARTINGCSV: ibm-storage-odf-operator.v1.0.1

Version of all relevant components (if applicable):
ODF 4.10

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)?
1

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 7 Mudit Agarwal 2022-08-09 15:17:36 UTC
As per the offline discussion, the current fix is enough for 4.11.0
Lets push the another fix to 4.11.z, moving it back to ON_QA

Comment 8 Elad 2022-08-16 08:53:39 UTC
Moving to VERIFIED based on regression testing results over 4.11 RC2

Comment 10 errata-xmlrpc 2022-08-24 13:55:09 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.11.0 security, enhancement, & bugfix 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:6156


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