Description of problem: Following bug 1533385, fail back won't clean a domain during fail back, only in case this domain is active. If the domain is in another status, maintenance for example, this domain will go through clean up. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Call fail back for a target setup that some of its storage domains are not written in the mapping var file and these domains are in maintenance Actual results: Fail back cleans the domains in maintenance even though they are written in the mapping var file Expected results: Fail back shouldn't clean these domains. Additional info:
Version-Release number of selected component (if applicable): ovirt-ansible-disaster-recovery-0.4-1.el7ev.noarch ansible-2.5.2-1.el7ae.noarch
Verified with the following code: --------------------------------------------------- ovirt-engine-4.2.4.1-0.1.el7.noarch vdsm-4.20.29-1.el7ev.x86_64 ovirt-ansible-disaster-recovery-1.1.0-1.el7ev.noarch Verified with the following scenario: --------------------------------------------------- Steps to Reproduce: 1. Call fail back for a target setup that some of its storage domains are not written in the mapping var file and these domains are in maintenance Actual results: Fail back NO LONGER cleans the domains in maintenance that are not written in the mapping var file Moving to VERIFIED
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.4 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.