In ODF 4.20 we have identified one issue related to the noobaa-db-pg-cluster-1-initdb-xxx pod deployment status, the pod never reaches running status and remains on "Init" status indefinitely.

$ oc -n openshift-storage get pods
noobaa-db-pg-cluster-1-initdb-ss9zv                               0/1     Init:0/1    0             14m

I can see this error on the pods describe.

$ oc describe pod noobaa-db-pg-cluster-1-initdb-v7k8c
Events:
  Type     Reason       Age                   From     Message
  ----     ------       ----                  ----     -------
  Warning  FailedMount  4m8s (x428 over 14h)  kubelet  MountVolume.MountDevice failed for volume "pvc-20b7ba2a-440a-4dff-971b-a8b393dbffa4" : rpc error: code = Internal desc = failed to set client address for ocs-storagecluster-cephblockpool/csi-vol-b55b37d9-d835-4538-bcc2-0c4b6059de19: failed to parse client address: failed to extract IP address, incorrect format: [fd98::4]:0/4279779476 

Also an error on the nooba-operator pod.

$ oc logs noobaa-operator-bff977f7c-m9f4v|grep -i 'level=error'
msg="cnpg:: got error creating the cluster resources in kubernetes api server. error: Internal error occurred: failed calling webhook \"mcluster.cnpg.io\": failed to call webhook: Post \"https://cnpg-controller-manager-service.openshift-storage.svc:443/mutate-postgresql-cnpg-noobaa-io-v1-cluster?timeout=10s\": no endpoints available for service \"cnpg-controller-manager-service\"" sys=openshift-storage/noobaatime="2025-08-27T17:28:27Z" level=error msg="Could not connect to system Connect(): ServiceMgmt not found"

As a result some ODF resources are not deployed properly, like the StorageCluster that remains in progressing status:
NAMESPACE           NAME                 AGE   PHASE         EXTERNAL   CREATED AT             VERSION
openshift-storage   ocs-storagecluster   16h   Progressing              2025-08-28T14:40:01Z   4.20.0

v4.20.0-56.stable    

Always

Deploy a MNO Compact cluster with the following configuration:
* Openshift-4.20.0-ec.5
* ODF-4.20.0-56.stable
* IPv6 network configuration
* StorageCluster with spec.network.ipFamily set to IPv6

noobaa-db-pg-cluster-1-initdb-xxx pod remains on "Init" status

noobaa-db-pg-cluster-1-initdb-xxx pod reaches "Running" status

We have an environment where this can be reproduced if required.