Bug 2128860 - [MDR] A PVC should be protected by only one VRG
Summary: [MDR] A PVC should be protected by only one VRG
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.11
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Annaraya Narasagond
QA Contact: avdhoot
URL:
Whiteboard:
: 2111163 (view as bug list)
Depends On:
Blocks: 2094357 2111163
TreeView+ depends on / blocked
 
Reported: 2022-09-21 17:55 UTC by Raghavendra Talur
Modified: 2024-09-10 10:35 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github RamenDR ramen pull 627 0 None open vrg: add vrg owner annotation to pv and pvc 2022-11-29 14:13:49 UTC

Description Raghavendra Talur 2022-09-21 17:55:56 UTC
Description of problem (please be detailed as possible and provide log
snippests):
It is possible that a user creates two DRPCs where both try to protect the same PVC on the managed cluster. This should be prevented as the result is non-deterministic.

There are multiple ways to prevent it from happening. One of which is VRG should ensure a PVC is protected by one instance of VRG and not more than one.


Version of all relevant components (if applicable):
4.11 and lower

Proposed solution: When a VRG protects a PVC it adds an annotation from ramen. We should look at adding a second annotation that links back to the VRG which protected it.

Comment 7 Raghavendra Talur 2022-12-08 14:44:45 UTC
*** Bug 2111163 has been marked as a duplicate of this bug. ***

Comment 18 Karolin Seeger 2023-04-18 03:59:37 UTC
Moving out of 4.13 as per comment #17

Comment 25 Mudit Agarwal 2023-09-11 06:54:23 UTC
Added exception flag


Note You need to log in before you can comment on or make changes to this bug.