Bug 1552620

Summary: Support last state of a target setup as part of the DR operation so user will be able to know the last known state of the target environment
Product: [oVirt] ovirt-ansible-collection Reporter: Maor <mlipchuk>
Component: disaster-recoveryAssignee: Tal Nisan <tnisan>
Status: CLOSED DEFERRED QA Contact: Avihai <aefrat>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: bugs, didi, lsvaty, ykaul
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: DR
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-01 14:45:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Maor 2018-03-07 12:59:01 UTC 
Description of problem:
Currently DR site-to-site support solution of fail-over and fail-back
It will be a benenfit if we can keep the state of the last operation which was done, so the admin will be aware what was last executed.
For example, if the admin will fail-over its setup, and will try to do that again after a week, the tool can prompt him a message indicating that fail-over was already done on this site. The user can then choose whether to clean the setup and start again, continue with the fail-over or abort the operation.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Michal Skrivanek 2020-03-18 15:44:33 UTC 
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
Comment 4 Michal Skrivanek 2020-03-18 15:49:33 UTC 
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
Comment 5 Michal Skrivanek 2020-04-01 14:45:35 UTC 
ok, closing. Please reopen if still relevant/you want to work on it.
Comment 6 Michal Skrivanek 2020-04-01 14:49:57 UTC 
ok, closing. Please reopen if still relevant/you want to work on it.