Bug 2128860

Summary: [MDR] A PVC should be protected by only one VRG
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Raghavendra Talur <rtalur>
Component: odf-drAssignee: Annaraya Narasagond <anarasag>
odf-dr sub component: ramen QA Contact: avdhoot <asagare>
Status: ASSIGNED --- Docs Contact:
Severity: urgent    
Priority: urgent CC: akrai, asagare, hnallurv, kseeger, mmuench, muagarwa, odf-bz-bot, pbyregow, sheggodu, srangana
Version: 4.11   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2094357, 2111163    

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