We never added it as a known issue in 4.11.0
I don't think doc test is required now.

VERIFICATION COMMENTS:-

Steps to Reproduce:
1. Configure RDR setup
2. Create sample application using repository as https://github.com/RamenDR/ocm-ramen-samples where the Branch is main and Path is busybox-odr
3. After applying DRPolicy to sample application
4. Give the PVC label while applying the DRpolicy PVC should be DR protected when application deployed via UI

PVCs are being protected. Attached the drpc,pod,pvc,vrg output.

_____________________________________________


Verified build - 4.11.3-5
ACM version - 2.6.2

namespace - app
drpc - app-placement-1-drpc

oc get drpc -n app app-placement-1-drpc -o yaml

apiVersion: ramendr.openshift.io/v1alpha1
kind: DRPlacementControl
metadata:
  creationTimestamp: "2022-11-04T05:03:01Z"
  finalizers:
  - drpc.ramendr.openshift.io/finalizer
  generation: 2
  labels:
    app: app
    cluster.open-cluster-management.io/backup: resource
  name: app-placement-1-drpc
  namespace: app
  resourceVersion: "1714745"
  uid: 0c40755c-7b43-46ad-9d5a-0b04e6460746
spec:
  drPolicyRef:
    name: dr-policy-10m
  placementRef:
    kind: PlacementRule
    name: app-placement-1
    namespace: app
  preferredCluster: kmanohar-clu1
  pvcSelector:
    matchLabels:
      appname: busybox
status:
  actionDuration: 30.024090852s
  actionStartTime: "2022-11-04T05:03:01Z"
  conditions:
  - lastTransitionTime: "2022-11-04T05:03:02Z"
    message: Initial deployment completed
    observedGeneration: 2
    reason: Deployed
    status: "True"
    type: Available
  - lastTransitionTime: "2022-11-04T05:03:01Z"
    message: Ready
    observedGeneration: 2
    reason: Success
    status: "True"
    type: PeerReady
  lastUpdateTime: "2022-11-04T07:53:31Z"
  phase: Deployed
  preferredDecision:
    clusterName: kmanohar-clu1
    clusterNamespace: kmanohar-clu1
  progression: Completed
  resourceConditions:
    conditions:
    - lastTransitionTime: "2022-11-04T05:03:02Z"
      message: Restored PV cluster data
      observedGeneration: 1
      reason: Restored
      status: "True"
      type: ClusterDataReady
    - lastTransitionTime: "2022-11-04T05:03:04Z"
      message: PVCs in the VolumeReplicationGroup are ready for use
      observedGeneration: 1
      reason: Ready
      status: "True"
      type: DataReady
    - lastTransitionTime: "2022-11-04T05:03:03Z"
      message: VolumeReplicationGroup is replicating
      observedGeneration: 1
      reason: Replicating
      status: "False"
      type: DataProtected
    - lastTransitionTime: "2022-11-04T05:03:04Z"
      message: Cluster data of all PVs are protected
      observedGeneration: 1
      reason: Uploaded
      status: "True"
      type: ClusterDataProtected
    resourceMeta:
      generation: 1
      kind: VolumeReplicationGroup
      name: app-placement-1-drpc
      namespace: app
      protectedpvcs:
      - busybox-pvc

oc get vrg,vr,pvc,pod -n app
NAME                                                               DESIREDSTATE   CURRENTSTATE
volumereplicationgroup.ramendr.openshift.io/app-placement-1-drpc   primary        Primary

NAME                                                             AGE     VOLUMEREPLICATIONCLASS                 PVCNAME       DESIREDSTATE   CURRENTSTATE
volumereplication.replication.storage.openshift.io/busybox-pvc   3h10m   rbd-volumereplicationclass-473128587   busybox-pvc   primary        Primary

NAME                                STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                  AGE
persistentvolumeclaim/busybox-pvc   Bound    pvc-8dc6f850-479d-49e7-a878-4bd03d0aa38d   5Gi        RWO            ocs-storagecluster-ceph-rbd   3h34m

NAME          READY   STATUS    RESTARTS   AGE
pod/busybox   1/1     Running   0          3h34m

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.11.3 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-2022:7912