Description of problem: VMs (re)validation not triggered by inventory changes. Version-Release number of selected component (if applicable): This is a regression introduced in 2.1.0-31. How reproducible: Always. Steps to Reproduce: 1. Edit a VM in RHV. 2. The (re)validation should be triggered within 10 seconds. 3. Actual results: The (re)validation may not be triggered within 10 seconds but will be triggered by the next periodic (every 10 minutes) check. Expected results: The (re)validation should be triggered within 10 seconds. Additional info:
2.1.0-34 / IIB:93583
Validation steps for example: Rename source RHV VM name from a valid name to a name that is not supported by Openshift.
Adding to the previous comment that the validation on MTV side, should be updated, further to the change on RHV side, after ~10 seconds, and not 10 minutes.
Verified on MTV build 2.1.0-48 / IIB 97916 Validation steps: Renamed source RHV VM name from a valid name to a name that is not supported by Openshift. On MTV side it was updated within ~10 seconds.
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