Yes, we have a bug in Ramen (VRG).
After the Replication State has moved to Secondary, we started processing VRG deletion.
As part of the deletion process, we try to make sure that the VR is not in degraded state. This is observed from the log through this log statement:
```
VolumeReplication and VolumeReplicationGroup state and autoresync match. Proceeding to status check {"VolumeReplicationGroup": "workload-2/drpc-2", "State": "secondary", "Finalize": true, "pvc": "workload-2/busybox-pvc-1"}
2022-08-04T18:09:17.417005253Z 1.6596365574169962e+09 INFO controllers.VolumeReplicationGroup.vrginstance controllers/vrg_volrep.go:1097 VolumeReplication resource for the pvc is syncing as Secondary (busybox-pvc-1/workload-2) {"VolumeReplicationGroup": "workload-2/drpc-2", "State": "secondary", "Finalize": true}
```
However, we fail to communicate that the VR is degraded to the higher layer of the call stack. That miscommunication ends up deleting the VR.
I am not sure if this is a regression or a day one issue. I will try to figure out that next. After that, we will create a patch sometime today.
Yes, we have a bug in Ramen (VRG). After the Replication State has moved to Secondary, we started processing VRG deletion. As part of the deletion process, we try to make sure that the VR is not in degraded state. This is observed from the log through this log statement: ``` VolumeReplication and VolumeReplicationGroup state and autoresync match. Proceeding to status check {"VolumeReplicationGroup": "workload-2/drpc-2", "State": "secondary", "Finalize": true, "pvc": "workload-2/busybox-pvc-1"} 2022-08-04T18:09:17.417005253Z 1.6596365574169962e+09 INFO controllers.VolumeReplicationGroup.vrginstance controllers/vrg_volrep.go:1097 VolumeReplication resource for the pvc is syncing as Secondary (busybox-pvc-1/workload-2) {"VolumeReplicationGroup": "workload-2/drpc-2", "State": "secondary", "Finalize": true} ``` However, we fail to communicate that the VR is degraded to the higher layer of the call stack. That miscommunication ends up deleting the VR. I am not sure if this is a regression or a day one issue. I will try to figure out that next. After that, we will create a patch sometime today.