Unexpected Power-Off of All VMs in a VApp After VApp-Level Migration

Products

• VMware Cloud Director

Issue/Introduction

• When migrating a VApp using the VApp-level migration option in VMware Cloud Director Availability (VCDA), all VMs within the source vApp are powered off unexpectedly after the migration completes.
• This issue occurs even when only a single VM from the vApp is selected for migration.
• This behaviour can lead to unintended downtime for workloads running in the remaining VMs of the vApp.

Environment

VMware Cloud Director Availability 4.7.3

Cause

This is known behaviour in VCDA where performing a Migrate action on a vApp replication can power off the entire source vApp, regardless of the number of VMs within the vApp being migrated.

Resolution

VCDA Engineering is aware of the issue and actively evaluating for a fix in a future release of VCDA. 

Workaround:

1. In VCD move the VM out of the vApp to new vApp and configure migration for this vApp. 
2. Create a replication not migration and manually do a power off of the source VM -> sync -> failover, this will not power off the source vapp.

NOTE: To be updated with any changes to this article, Subscribe to this article.