Bug 1977329
| Summary: | [RFE] Allow DBStorageClass to be set from Storage Cluster CR for Noobaa | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Container Storage | Reporter: | Kaustav Majumder <kmajumde> |
| Component: | ocs-operator | Assignee: | Kaustav Majumder <kmajumde> |
| Status: | CLOSED ERRATA | QA Contact: | suchita <sgatfane> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.8 | CC: | agantony, etamir, jarrpa, madam, mbukatov, muagarwa, nbecker, nberry, ocs-bugs, rcyriac, sabose, sgatfane, sostapov |
| Target Milestone: | --- | Keywords: | AutomationBackLog, Bugfix, FutureFeature |
| Target Release: | OCS 4.8.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | v4.8.1-177.ci | Doc Type: | Enhancement |
| Doc Text: |
Previously, it was not possible to deploy the Multicloud Object Gateway (MCG) with other storage classes as the noobaa-db pod consumed storage from the `ocs-ceph-rbd` storage class. With this update, you can set the noobaa-db storageclass name from the Storage Cluster CR. This allows MCG deployment without storage consumption from the `ocs-ceph-rbd` as the Storage Cluster spec includes `DbStorageClassName` in the `MultiCloudGatewaySpec`.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-08-30 14:19:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kaustav Majumder
2021-06-29 13:23:23 UTC
If I remember correctly this need is coming from the managed add-on. We had some discussion about this earlier today and we're still deciding whether we need any actual automation in OCS itself or if it's something the deployer can handle. If we need something in OCS it may be acceptable to have this in OCS 4.8.z, so moving it there and marking it as a potential blocker. Verification use case: deploy StorageCluster with NooBaa without Ceph using this feature Jose, can you confirm if we need change in 4.9 too as well to pass the StorageClass for NooBaa DB PV? We will need this, yes. If nothing else, we can't just add this new API in 4.8 and then have it disappear in 4.9. But we don't need a BZ for 4.9, just submit a PR to master and it can merge without a BZ. The only requirement is that the release-4.8 version be as similar to the master PR as possible, if not identical. This BZ already has dev_ack+, so we need someone from QE to give qa_ack+. Please fill the doc text In a NON-Managed cluster the Storage Cluster CR needs to be updated as follows :- ``` multiCloudGateway: reconcileStrategy: "" dbStorageClass: <test-storage-class-name> ``` After deployment succeeds check the noobaa CR oc get noobaa noobaa -oyaml The noobaa CR should have the following under spec: ``` dbStorageClass : <test-storage-class-name> pvPoolDefaultStorageClass : <test-storage-class-name> ``` ` @nberry I overlooked this before, sorry for that. The spec in multiCloudGateway should be dbStorageClassName and not dbStorageClass. so it should look like this ``` multiCloudGateway: reconcileStrategy: "" dbStorageClassName: <test-storage-class-name> ``` 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 Container Storage 4.8.1 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-2021:3312 |