VMware Cloud Director Availability (VCDA) Fails to Create New Protections After Upgrade to 4.7.3

Products

• VMware Cloud Director

Issue/Introduction

• After upgrading to version 4.7.3, the creation of new protections failed with the error message "Unexpected VMware Cloud Director error."
• In VCDA destination cloud.log, you will see the similar error message:

  DEBUG - [UI-xxxxx-xxxx-xxxx-xxxx-xxxxxxxx-xxxx-xa-yx] [task-poller-3] c.vmware.h4.cloud.job.VmReplicationJob   : Creation of rt vm failed.

  com.vmware.vcloud.client.exception.VcloudException: HTTP Response code: 500

  
   Task 4xxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx (WorkflowInfo{type='start', resourceType='vmReplication', resourceId='C4-xxxxxxxx-xxxxxx-xxxxx-xxxx-xxxxxxxxx', isPrivate=false, resourceName='null'}) has failed

  com.vmware.h4.cloud.api.exceptions.VcloudError: Unexpected vCloud Director error.

  2024-12-02 04:51:59.678 DEBUG - [UI-ID] [job-13] com.vmware.h4.cloud.job.VmStopJob        : Stopping replication C4-xxxxxxxx-xxxxxx-xxxxx-xxxx-xxxxxxxxx
2024-12-02 04:51:59.680  WARN - [UI-ID] [job-13] com.vmware.h4.cloud.job.VmStopJob        : Replication C4-xxxxxxxx-xxxxxx-xxxxx-xxxx-xxxxxxxxx has no h4 replication id.
2024-12-02 04:51:59.707  INFO - [UI-ID] [job-13] com.vmware.h4.cloud.job.VmStopJob        : Attempting to remove placement independent disk for C4-xxxxxxxx-xxxxxx-xxxxx-xxxx-xxxxxxxxx
2024-12-02 04:51:59.797  INFO - [UI-ID] [job-13] c.v.h.c.s.DatastoreManagementService     : Independent disk C4-xxxxxxxx-xxxxxx-xxxxx-xxxx-xxxxxxxxx is already deleted

Environment

VMware Cloud Director Availability 4.7.x

Cause

The creation of new protections was being blocked by a task in the VMware Cloud Director (VCD) UI, specifically the vcdcomposeVapp task. This blocking task caused the VM creation to fail, triggering an HTTP 500 error during replication. The task was halting the creation process, and after 5 seconds, VCD received an abort event, which stopped the process.

Resolution

In order to resolve the issue, follow the below mentioned steps:

• Log in to the VCD UI.
• In the VCD UI, under Extensibility > Blocking Tasks.
• Check for blocking/resume task.
• It will be configured, with the vcdcomposeVapp task marked as checked, which is causing the block.
• Disable the blocking task (vcdcomposeVapp) to allow the VM creation process to proceed without interruption.