Bug 1437865

Summary: Geo-rep schedule should delete VM snapshot post gluster geo-rep checkpoint is synced
Product: [oVirt] ovirt-engine Reporter: SATHEESARAN <sasundar>
Component: BLL.GlusterAssignee: Sahina Bose <sabose>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: urgent Docs Contact:
Priority: high    
Version: 4.1.1.7CC: bmcclain, bugs, cshao, lveyde, sabose, seamurph, ycui
Target Milestone: ovirt-4.1.2Flags: rule-engine: ovirt-4.1+
rule-engine: blocker+
bmcclain: planning_ack+
sabose: devel_ack+
sasundar: testing_ack+
Target Release: 4.1.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-25 06:43:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1277939    

Description SATHEESARAN 2017-03-31 11:07:30 UTC 
Description of problem:
------------------------
With the existing logic of remote sync, VM snapshots are initiated and completed, but deleted before geo-rep sync has reached checkpoint.

VM snapshots should be deleted only after geo-rep checkpoint is reached

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHV 4.1.1-6

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Create a gluster data domain backed with replica 3 sharded volume
2. Create a gluster geo-rep session
3. Create a remote data sync setup
4. Notice for the flow of events

Actual results:
---------------
VM snapshots are deleted before the gluster geo-rep checkpoint is reached

Expected results:
-----------------
VM snapshots should be deleted only after geo-rep checkpoint is reached
Comment 2 SATHEESARAN 2017-05-23 20:11:47 UTC 
Tested with RHV-4.1.2.2

VM snapshot deletion is happening post the geo-rep checkpoint is reached