Snapshot creation fails for a VM replicated and failed over by vCloud Availability for Cloud-to-Cloud DR 1.x

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• Creating a snapshot of a VM you have failed over fails and the VM has the following status in the vCloud Director GUI:

Error performing operation

• Clicking on the status in vCloud Director, you see a similar message:

[ f8cac2c1-5884-44dc-a1af-98c7f57aa83e ] Underlying system error:
An error occurred while taking a snapshot: The filename is too long.
An error occurred while saving snapshot file "/vmfs/volumes/5ae8642b-52087303-08be-005056017817/C4-6fce47db-8c62-4b36-908a-fd2cc8274da4/vRealize Operations Manager Appliance (100b8713-9085-46cd-923e-69130f1f3b95)-Snapshot1.vmsn".
An error occurred while saving the snapshot: The filename is too long.
vCenter Server task (moref: task-5191) failed in vCenter Server 'Resource vCenter 01' (0d27b38f-c580-4d7d-9f32-46720ff638af).
 - An error occurred while saving the snapshot: The filename is too long.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCloud Availability for Cloud-to-Cloud DR 1.x
VMware Cloud Director for Service Provider 9.x

Cause

This issue occurs because, in vCloud Availability for Cloud-to-Cloud DR, the target VMDK file is created with a unique UUID at the start of the filename. When a vCD VM with a name of at least 31 characters long is replicated with vCloud Availability, with the addition of the vCloud Availability UUID at the start of the filename and the vCloud Director UUID at the end, you exceed the character limit for a file when attempting to create the snapshot.

Resolution

This is a known issue affecting VMs replicated with vCloud Availability for Cloud-to-Cloud DR 1.x.
Currently, there is no resolution.