MTV fails in warm migration from VMWare vCenter although cold migration works correctly

Solution Unverified - Updated -

Issue

  • importer pod fails with CrashLoopBackOff state.
  • Its logs show the following error messages
2025-04-03T02:42:54.206085937Z E0403 02:42:54.187511       1 vddk-datasource_amd64.go:281] Unable to connect to vCenter: Post "https://source-provider/sdk": Service Unavailable
2025-04-03T02:42:54.206085937Z E0403 02:42:54.187548       1 vddk-datasource_amd64.go:841] Unable to log in to VMware: Post "https://source-provider/sdk": Service Unavailable
2025-04-03T02:42:54.206085937Z E0403 02:42:54.187554       1 importer.go:347] Post "https://source-provider/sdk": Service Unavailable

2025-02-16T07:14:45.569458009Z E0216 07:14:45.569433       1 vddk-datasource_amd64.go:281] Unable to connect to vCenter: Post "https://source-provider/sdk": remote error: tls: handshake failure
2025-02-16T07:14:45.569472503Z E0216 07:14:45.569454       1 vddk-datasource_amd64.go:841] Unable to log in to VMware: Post "https://source-provider/sdk": remote error: tls: handshake failure
2025-02-16T07:14:45.569472503Z E0216 07:14:45.569460       1 importer.go:347] Post "https://source-provider/sdk": remote error: tls: handshake failure
  • Since cold migration works correctly, there is no network connectivity issue.

Environment

  • Migration Toolkit for Virtualization 2.7
  • VMWare vCenter

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content