Description of problem: In addition to VM validation triggered by changes - Every 10 minutes, the controller searches the DB for VMs that need to be validated. A VM needs to be validated (or re-validated) when: - The vm.revision != vm.revisionValidated - The vm.policyVersion != (latest policy version returned by validation service). The bug is: The version for oVirt and vSphere are different but the path used by the controller in the URL was hard coded for /vmware/. As a result, when getting the version intended to be match for oVirt (latest=1), it was the policy version for vSphere (latest-5). Version-Release number of selected component (if applicable): 2.1.0 How reproducible: Always. Steps to Reproduce: 1. Create a RHV provider. 2. Observe every 10 minutes, all of the RHV VMs get re-validated. 3. Actual results: Every 10 minutes, all of the RHV VMs get re-validated. Expected results: Only re-validated as needed. Additional info:
2.1.0-34 / IIB:93583
verify MTV_2.1.0-44 / IIB 96817
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Migration Toolkit for Virtualization 2.1.0), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2021:3278