Machine [<VMNAME1>] already belongs to a deployment.
Machine [<VMNAME2>] already belongs to a deployment....
Managed
' or 'Deployed
' but rather as 'Discovered
' machines.This can happen if the VM is still tied to the onboarding plan and needs a cleanup.
To resolve the issue, clean up the machine's custom properties via Rest API to ensure there are no references to a deployment:
For more information, see the Getting Your Authentication Token section in the VMware Aria Automation Programming Guide.
Get the compute ID of the affected machines:
Note:
AriaAutoFQDN
with the FQDN of your Aria Automation environment.VM-Name001
with the affected VM name.67705272-418c-30a3-9b0d-eaf2eeedb117
). Use this ID as <compute_id>
below.Invoke a GET API call to the following URL to see the custom properties of the machines:
In the body of the response, search for the customProperties section of the VMs. If any of the following properties are populated with a value, remove the key-value pairs:
Set to null
for the following links:
descriptionLink
orgAuthLink
projectAuth
ownerAuthLink
For example: descriptionLink: " "
Edit the customProperties
map to remove the following key-value pairs:
__composition_context_id
__deployment_id
__component_type_id
__blueprint_resource_id
__groupResourcePlacementLink
__relocation_origin
Note: You must remove both the key and the value.
Remove from tenantLinks
where XXX
are values specific to the machine:
/owner/provisioning/auth/csp/users/XXX
/provisioning/resources/projects/XXX
Invoke a PUT API request to the same URL containing the updated request body with properties removed:
Attempt again to onboard the machines.
If the previous instructions do not work, proceed to Manually unregister an onboarded machine from a deployment in case of an unregister action failure as next steps.