How to change NooBaa DB access mode from RWOP to RWO in standalone MCG deployments?

Solution Verified - Updated -

Issue

  • MCG standalone deployment fails to provision NooBaa DB PVC due to unsupported RWOP access mode:
  Normal   Provisioning          5m12s (x583 over 37h)  csi.hpe.com_<domain>_<xxxx>  External provisioner is provisioning volume for claim "openshift-storage/db-noobaa-db-pg-0"
  Warning  ProvisioningFailed    4m50s (x530 over 37h)  csi.hpe.com_<domain>_<xxxx>  rpc error: code = Unavailable desc = Failed to get storage provider from secrets, Request failed with status code 500 and errors Error code (Internal Server Error) and message (sending the unrecognized error as an InternalServer Error to CSI)
  Normal   ExternalProvisioning  1s (x9330 over 37h)    persistentvolume-controller                                                                      Waiting for a volume to be created either by the external provisioner 'csi.hpe.com' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered.
  • How to configure ReadWriteOnce (RWO) access mode for NooBaa DB ?
  • Fixing NooBaa DB PVC provisioning failures when CSI driver does not support ReadWriteOncePod (RWOP)
  • Switching NooBaa DB Access Mode from RWOP to RWO in Standalone MCG deployment

Environment

  • Red Hat OpenShift Data Foundation(RHODF)
    • 4.16 - 4.18
    • 4.19+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content