Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2051504

Summary:	Change vddkInitImage to be set via MTV API for MTV 2.3 or later
Product:	Migration Toolkit for Virtualization	Reporter:	Ilanit Stein <istein>
Component:	Controller	Assignee:	Sam Lucidi <slucidi>
Status:	CLOSED ERRATA	QA Contact:	Amos Mastbaum <amastbau>
Severity:	unspecified	Docs Contact:	Richard Hoch <rhoch>
Priority:	unspecified
Version:	2.2.0
Target Milestone:	---
Target Release:	2.3.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:	2022-04-04 18:03:45 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 Ilanit Stein 2022-02-07 11:36:01 UTC

Description of problem:
Sam Lucidi:

In MTV 2.3, the vddk init image will need to be specified on the Provider CR for vSphere migrations. This is due to bug 2031033, which means that we can't have  CNV to propagating the value to CDI. Below is an example of a vSphere Provider CR with the vddkInitImage specified.

Best,
Sam

kind: Provider
apiVersion: forklift.konveyor.io/v1beta1
metadata:
  name: boston
  namespace: konveyor-forklift
spec:
  url: "https://vcenter.v2v.bos.redhat.com/sdk"
  type: vsphere
  settings:
    vddkInitImage: quay.io/slucidi/vddk-test:latest
  secret:
    namespace: konveyor-forklift
    name: boston

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 1 Ilanit Stein 2022-02-13 06:53:51 UTC

Verified on MTV-2.3.0-23.
VM migration from VMware was successful, and used the vddk init image taken from the the VMware provider CR.

Comment 5 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