Aria Automation Deployments fails with "errors:null" message

Products

• VMware Aria Suite

Issue/Introduction

Deployments are failing due to a conflict with existing hostnames in Active Directory (AD). When attempting to create a new machine in AD, the chosen hostname already exists, causing the operation to fail.

Fails with the error "[ad-integration] Active Directory Action CREATE_MACHINE for request uuid failed with errors:null"

Failure logs from the workflow:

{
  "user": "XXXXXXXX\\XXXXX",
  "baseDN": "DC=example,DC=COM",
  "server": "ldap://example.com:389",
  "computes": [
    {
      "relativeDN": "OU=SERVERS",
      "computeName": "hostname"
    }
  ],
  "__metadata": {
    "headers": {
      "tokenId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
    }
  },
  "actionType": "CREATE_MACHINE",
  "alternativeHost": "",
  "connectionTimeout": "10",
  "authCredentialsLink": "/core/auth/credentials/xxxx-xxxxx-xxxx-xxxxxxx"
}
{
  "status": "failure",
  "actionType": "CREATE_MACHINE",
  "machineName": "Hostname",
  "Hostname": {
    "error": "on_create_machine_exists",
    "status": "failure"
  }
}

The error message in the logs indicates "on_create_machine_exists," signifying a conflict with an existing hostname.

The provided sample logs show the attempt to create a machine named "hostname" within the "OU=SERVERS" container

 

Environment

VMware Aria Automation 8.x

Cause

The deployment process attempted to create a new machine in Active Directory with a name that already existed.  Active Directory enforces unique machine names, resulting in the "on_create_machine_exists" error when encountering a duplicate entry.

 

Resolution

To resolve this issue you can manually delete the active directory computer object of the machine

For example the Virtual Machine name is 'VM123'

1. Delete the Active Directory Computer Object: Open Active Directory Users and Computers, locate the computer object for the VM (e.g., VM123), right-click, and select Delete.

2. Retry the Deployment: After deleting the computer object, start the deployment process again, which should now complete successfully.