Bug 2264002

I don't understand the test procedure. how to verify this bz?

I dont see the logs of csi-rbdplugin container of rbd provisioner pods.

ODF Version:4.15.0-155
OCP Version: 4.15.0
RDR cluster
platform: vsphere

1.Craete PVC [SC=ceph-rbd]:
oviner~/ClusterPath/auth$ oc get pvc -n openshift-storage pvc-test 
NAME       STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                  AGE
pvc-test   Bound    pvc-35fea3a4-849d-442c-803a-b4391749b6ec   2Gi        RWO            ocs-storagecluster-ceph-rbd   59s

oviner~/ClusterPath/auth$ oc get pvc -n openshift-storage pvc-test -o yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  annotations:
    pv.kubernetes.io/bind-completed: "yes"
    pv.kubernetes.io/bound-by-controller: "yes"
    reclaimspace.csiaddons.openshift.io/cronjob: pvc-test-1709835591
    reclaimspace.csiaddons.openshift.io/schedule: '@weekly'
    volume.beta.kubernetes.io/storage-provisioner: openshift-storage.rbd.csi.ceph.com
    volume.kubernetes.io/storage-provisioner: openshift-storage.rbd.csi.ceph.com
  creationTimestamp: "2024-03-07T18:19:51Z"
  finalizers:
  - kubernetes.io/pvc-protection
  name: pvc-test
  namespace: openshift-storage
  resourceVersion: "1916048"
  uid: 35fea3a4-849d-442c-803a-b4391749b6ec
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 2Gi
  storageClassName: ocs-storagecluster-ceph-rbd
  volumeMode: Filesystem
  volumeName: pvc-35fea3a4-849d-442c-803a-b4391749b6ec
status:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 2Gi
  phase: Bound


2.Create VolumeReplicationClass:
$ oc create -f VolumeReplicationClass.yaml 
volumereplicationclass.replication.storage.openshift.io/volumereplicationclass-sample created

oviner~/ClusterPath/auth$ cat VolumeReplicationClass.yaml
apiVersion: replication.storage.openshift.io/v1alpha1
kind: VolumeReplicationClass
metadata:
  name: volumereplicationclass-sample
spec:
  provisioner: example.provisioner.io
  parameters:
    replication.storage.openshift.io/replication-secret-name: secret-name
    replication.storage.openshift.io/replication-secret-namespace: secret-namespace
    # schedulingInterval is a vendor specific parameter. It is used to set the
    # replication scheduling interval for storage volumes that are replication
    # enabled using related VolumeReplication resource
    schedulingInterval: 1m

3.Create VolumeReplication:
$ oc create -f VolumeReplication.yaml 
volumereplication.replication.storage.openshift.io/my-vrt2 created

$ cat VolumeReplication.yaml 
apiVersion: replication.storage.openshift.io/v1alpha1
kind: VolumeReplication
metadata:
  name: my-vrt2
  namespace: openshift-storage
spec:
  volumeReplicationClass: volumereplicationclass-sample
  replicationState: primary
  replicationHandle: replicationHandle # optional
  dataSource:
    kind: PersistentVolumeClaim
    name: pvc-test

4.Check the logs of csi-rbdplugin container of rbd provisioner pods
$ oc get pods | grep csi-rbdplugin-provisioner
csi-rbdplugin-provisioner-698f984d84-hblzp                        7/7     Running     1 (5h21m ago)   29h
csi-rbdplugin-provisioner-698f984d84-zc66w                        7/7     Running     1 (5h8m ago)    29h

oviner~/ClusterPath/auth$ oc logs csi-rbdplugin-provisioner-698f984d84-zc66w -n openshift-storage --all-containers | grep bytes_per_second
oviner~/ClusterPath/auth$ oc logs csi-rbdplugin-provisioner-698f984d84-hblzp -n openshift-storage --all-containers | grep bytes_per_second
oviner~/ClusterPath/auth$

Yati, 
The odr-cluster-operator.v4.15.0-rhodf not in Succeeded mode, Do you think I dont see the log because odr-cluster-operator.v4.15.0-rhodf issue? 

$ oc get csv odr-cluster-operator.v4.15.0-rhodf
NAME                                 DISPLAY                         VERSION        REPLACES   PHASE
odr-cluster-operator.v4.15.0-rhodf   Openshift DR Cluster Operator   4.15.0-rhodf              Succeeded

    Message:               installing: waiting for deployment ramen-dr-cluster-operator to become ready: deployment "ramen-dr-cluster-operator" not available: Deployment does not have minimum availability.

Hi Oded,

Why is this in FailedQA because:
1. You didn't the logs of csi-rbdplugin container of rbd provisioner pods OR
2. You are not able to see the DR related logs there?

If it is first one then it is nothing to do with this bug and you need to check why logs are not accessible.
If it is second one and ramen-dr-cluster-operator is not available then it is expected.

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.15.0 security, enhancement, & 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-2024:1383