Bug 1978351 - "VM Revision Validated" field does not increment correctly after RHV VM validation
Summary: "VM Revision Validated" field does not increment correctly after RHV VM valid...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: Controller
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2.1.0
Assignee: Jeff Ortel
QA Contact: Tzahi Ashkenazi
Avital Pinnick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-01 15:52 UTC by Jeff Ortel
Modified: 2021-08-26 07:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-08-26 07:09:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2021:3278 0 None None None 2021-08-26 07:09:18 UTC

Description Jeff Ortel 2021-07-01 15:52:27 UTC
Description of problem:

RHV VMs validated but VM.revisionValidated always 1 behind the VM.revsion.

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


How reproducible:

Always.


Steps to Reproduce:
1. Create a provider and view the inventory.
2.
3.

Actual results:

VM.revisionValidated always 1 behind the VM.revsion.



Expected results:

VM.revisionValidated = VM.revsion after validation.


Additional info:

Comment 2 Fabien Dupont 2021-07-01 21:10:46 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:29 UTC
Please verify with build 2.10-19 / iib:88267.

Comment 4 Amos Mastbaum 2021-08-17 08:35:19 UTC
Veified:
MTV 2.1.0-48 / IIB 97916
cnv 4.8.1-18

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


Note You need to log in before you can comment on or make changes to this bug.