Bug 2187251 - sync ocs and odf with the latest rook
Summary: sync ocs and odf with the latest rook
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-operator
Version: 4.13
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ODF 4.13.0
Assignee: Nitin Goyal
QA Contact: Aviad Polak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-17 09:01 UTC by Nitin Goyal
Modified: 2023-08-09 17:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-06-21 15:25:03 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ocs-operator pull 2012 0 None Merged update rook to 1.11.4 2023-04-17 09:01:59 UTC
Github red-hat-storage ocs-operator pull 2013 0 None open Bug 2187251:[release-4.13] update rook to 1.11.4 2023-04-17 12:24:23 UTC
Github red-hat-storage odf-operator pull 312 0 None open godeps: update ocs-operator apis 2023-04-17 09:47:04 UTC
Github red-hat-storage odf-operator pull 313 0 None open Bug 2187251:[release-4.13] godeps: update ocs-operator apis 2023-04-17 13:24:25 UTC
Red Hat Product Errata RHBA-2023:3742 0 None None None 2023-06-21 15:25:18 UTC

Description Nitin Goyal 2023-04-17 09:01:02 UTC 
Description of problem (please be detailed as possible and provide log
snippets): update rook apis and rook image in the ocs-operator and get those changes in the odf-operator.
Comment 9 errata-xmlrpc 2023-06-21 15:25:03 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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and 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/RHBA-2023:3742
Note You need to log in before you can comment on or make changes to this bug.