Bug 1978355

Summary:	VM validation results are not displayed immediately
Product:	Migration Toolkit for Virtualization	Reporter:	Jeff Ortel <jortel>
Component:	Controller	Assignee:	Jeff Ortel <jortel>
Status:	CLOSED ERRATA	QA Contact:	David Vaanunu <dvaanunu>
Severity:	medium	Docs Contact:	Avital Pinnick <apinnick>
Priority:	high
Version:	2.1.0	CC:	dvaanunu, fdupont
Target Milestone:	---
Target Release:	2.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-26 07:09:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jeff Ortel 2021-07-01 16:06:42 UTC

Description of problem:

Fix updating VMs with batched validation result. When something failed or the revision of the validated VM no longer matched the latest VM, we needed to continue processing other task results instead of returning. As a result, subsequent task results were not updating their VMs and VMs would remain un-validated (in the DB) until the next schedule validation or an update triggered (re)validation of the VM.

This is a regression introduced late in 2.0.0 performance/scale fixes that also affects vSphere.

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

2.1

How reproducible:

Can't really be reproduced except watching the inventory and notice that some VMs take a longer time than expected to reflect validation result.

Steps to Reproduce:
1. Just watch the inventory for a while.
2.
3.

Actual results:

Delay in VM not reflecting validation result.


Expected results:

VMS should reflect validation result immediately.

Additional info:

Comment 1 Jeff Ortel 2021-07-01 16:07:21 UTC

https://github.com/konveyor/forklift-controller/pull/297

Comment 2 Fabien Dupont 2021-07-01 21:13:06 UTC

This is a bug with small fix. I'm in favor of fixing it in MTV 2.1.

Comment 3 Fabien Dupont 2021-07-05 19:51:11 UTC

Please verify with build 2.10-19 / iib:88267.

Comment 4 David Vaanunu 2021-08-12 13:12:18 UTC

verify MTV_2.1.0-44 / IIB 96817

Comment 7 errata-xmlrpc 2021-08-26 07:09:10 UTC

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