Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Since we added a VRG on the secondary cluster we have a random failure when deleting the DRPC after relocate. When this happens, we find the PVC in terminating state on the secondary cluster, and the VR and VRG are never deleted. This change avoids this issue by deleting the secondary VRG first, and deleting the primary VRG only after the secondary VRG was deleted. When we wait for the deletion of a VRG, we must requeue the request. In a real system we may be able to return success and detect the deletion when a watched resource changes, but in unit tests breaks if we don't requeue the request. The only way to do this with the current code is to return an error. This logs many errors in the log during deletion, like: ERROR Secondary VRG manifestwork deletion in progress very noisy stacktrace... ERROR Primary VRG manifestwork deletion in progress very noisy stacktrace... More work is needed to silence the expected errors. Fixes: RamenDR#1659 Signed-off-by: Nir Soffer <[email protected]>
- Loading branch information