ERROR: "Internal Server Error Failed to configure drs Rule" when attempting to create Anti-Affinity rules in Cloud Director

Products

• VMware Cloud Director
• VMware Telco Cloud Platform

Issue/Introduction

• When attempting to create Anti-Affinity rules in Cloud Director 10.3x versions:
  One or more exceptions have occurred - Internal Server Error

• Unable to create Anti Affinity rules in Cloud Director for auto imported virtual machines.

• Error message while creation of AntiAffinity/Affinity rules in cloud director show:

  Internal Server Error - Failed to configure drs Rule id <Rule id> in cluster ManagedObjectReference: type = ClusterComputeResource, value = domain-######, serverGuid = null

Environment

VCD 10.3.x, 10.3.3.2

TCP 2.2

Cause

• This Internal Server Error is triggered because the cloud_uuid is missing in both the Cloud Director database and in the VM VMX file in vCenter.

• Conflicting anti-affinity rules in vCenter are blocking the placement engine.

• These rules were likely remnants from a VNF termination process preceding the upgrade activity.

• Cloud Director creates drsShellVm to ensure affinity rules are created

 

Resolution

This is a known issue affecting VMware Cloud Director 10.3.x versions.
The issue is resolved in VMware Cloud Director 10.4, available at Broadcom Downloads.

Workaround:

If you dont see the rule in vcd UI affinity rule and you see the rule in vcenter server, perform the following:

1. Delete the drs rule in vcenter.
2. Search in vcenter for drsShellVM and you will find one that will say drsShellVM<UUID> that will show up in the esxi host cluster.
3. Delete the drsShellVM from the esxi host cluster in vcenter.
4. After deletion of rule and drsShellVM the drs affinity/anti-affinity rule will create.