Bug 2051508 - Change vddkInitImage to be set via MTV UI for MTV 2.3 or later
Summary: Change vddkInitImage to be set via MTV UI for MTV 2.3 or later
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Migration Toolkit for Virtualization
Classification: Red Hat
Component: User Experience
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 2.3.0
Assignee: Mike Turley
QA Contact: Igor Braginsky
Richard Hoch
URL:
Whiteboard:
Depends On:
Blocks: 2051655
TreeView+ depends on / blocked
 
Reported: 2022-02-07 11:40 UTC by Ilanit Stein
Modified: 2022-04-04 18:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2051655 (view as bug list)
Environment:
Last Closed: 2022-04-04 18:03:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github konveyor forklift-ui pull 909 0 None open Bug 2051508: Add field for VDDK init image to vmware provider form 2022-02-07 17:28:23 UTC
Red Hat Product Errata RHEA-2022:1183 0 None None None 2022-04-04 18:03:54 UTC

Description Ilanit Stein 2022-02-07 11:40:04 UTC 
Description of problem:
further to Bug 2051504 Change of having vddkInitImage set via MTV API for MTV-2.3 and above, please add to "Add provider" the VddkInitImage settings.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Ilanit Stein 2022-02-13 06:55:33 UTC 
Verified on CNV-4.10/MTV-2.3.0-24
VM migration from VMware was successful, and used the vddk init image taken from the the VMware provider, set in Migration UI.
Comment 6 errata-xmlrpc 2022-04-04 18:03:45 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 (MTV 2.3.0 images), 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-2022:1183
Note You need to log in before you can comment on or make changes to this bug.