Bug 2049718 - provider/consumer Mode: rook-ceph-csi-config configmap needs to be updated with the relevant subvolumegroup information
Summary: provider/consumer Mode: rook-ceph-csi-config configmap needs to be updated wi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: rook
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ODF 4.10.0
Assignee: Sébastien Han
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-02 15:30 UTC by Kesavan
Modified: 2023-08-09 17:03 UTC (History)
6 users (show)

Fixed In Version: 4.10.0-148
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-13 18:52:41 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage rook pull 340 0 None open Bug 2049718: subvolumegroup: handle external mode 2022-02-04 13:44:05 UTC
Github rook rook pull 9694 0 None open subvolumegroup: add external capability 2022-02-02 15:35:19 UTC
Red Hat Product Errata RHSA-2022:1372 0 None None None 2022-04-13 18:52:59 UTC

Description Kesavan 2022-02-02 15:30:26 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
In provider and consumer mode, the cephfs storageclass for the created subvolume group needs to be created in the consumer cluster and it requires clusterID from rook-ceph-csi-config config map.    

A mechanism is required from rook to update the rook-ceph-csi-config config map with required clusterID and subvolume group information in the consumer cluster
Comment 8 Sébastien Han 2022-03-09 09:47:54 UTC 
Neha, the only thing we need to verify is that after the creation of the cephfilesystemsubvolumegroups CRD in the consumer cluster, the csi configmap gets updated.
There is nothing to check in the provider.
It looks like it did, so we can move to VERIFIED.

Thanks.
Comment 11 errata-xmlrpc 2022-04-13 18:52:41 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.10.0 enhancement, security & 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/RHSA-2022:1372
Note You need to log in before you can comment on or make changes to this bug.