Skip to main content

 "Machine already belongs to a deployment" failure when trying to onboard machines in Aria Automation

https://knowledge.broadcom.com/external/article?articleNumber=314703

Products

VMware Aria Suite

Issue/Introduction

Symptoms:
  • When attempting to onboard machines in Aria Automation you get error:

Machine [<VMNAME1>] already belongs to a deployment.
Machine [<VMNAME2>] already belongs to a deployment....

  • Under Cloud Assembly > Resources > Virtual Machines the machines do not show as 'Managed' or 'Deployed' but rather as 'Discovered' machines.
  • No Deployment appears to have them as resources in the Aria Automation UI.

Environment

  • VMware Aria Automation 8.x

Cause

This can happen if the VM is still tied to the onboarding plan and needs a cleanup.

Resolution

To resolve the issue, clean up the machine's custom properties via Rest API to ensure there are no references to a deployment:

Prerequisites:

  • You have backups of the VMware Aria Automation 8.x appliance(s).
  • You must back up all VMware Aria Automation appliances at the same time — simultaneously for all nodes.
  • If you are making the snapshots manually, you must start the snapshots of the second and third node no more than 40 seconds after you start the snapshots for the first node.
  • When you back up the VMware Aria Automation appliance, disable in-memory snapshots and enable quiescing (quiescing is a requirement only for version 8.9 and newer).

Acquire an Authentication Token:

For more information, see the Getting Your Authentication Token section in the VMware Aria Automation Programming Guide.

Procedure: Remove the stale entries using the REST API

  1. Get the compute ID of the affected machines:

    GET https://AriaAutoFQDN/deployment/api/resources?search=VM-Name001

    Note:

    • Replace AriaAutoFQDN with the FQDN of your Aria Automation environment.
    • Replace VM-Name001 with the affected VM name.
    • From the output, take the ID (e.g., 67705272-418c-30a3-9b0d-eaf2eeedb117). Use this ID as <compute_id> below.

  2. Invoke a GET API call to the following URL to see the custom properties of the machines:

    GET https://AriaAutoFQDN/provisioning/uerp/resources/compute/<compute_id>

  3. 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

  4. Invoke a PUT API request to the same URL containing the updated request body with properties removed:

    PUT https://AriaAutoFQDN/provisioning/uerp/resources/compute/<compute_id>

  5. 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.

Comments

Post a Comment

Popular posts from this blog

  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
Post a Comment
Read more

57 Tips Every Admin Should Know

Active Directory 1. To quickly list all the groups in your domain, with members, run this command: dsquery group -limit 0 | dsget group -members –expand 2. To find all users whose accounts are set to have a non-expiring password, run this command: dsquery * domainroot -filter “(&(objectcategory=person)(objectclass=user)(lockoutTime=*))” -limit 0 3. To list all the FSMO role holders in your forest, run this command: netdom query fsmo 4. To refresh group policy settings, run this command: gpupdate 5. To check Active Directory replication on a domain controller, run this command: repadmin /replsummary 6. To force replication from a domain controller without having to go through to Active Directory Sites and Services, run this command: repadmin /syncall 7. To see what server authenticated you (or if you logged on with cached credentials) you can run either of these commands: set l echo %logonserver% 8. To see what account you are logged on as, run this command: ...
Post a Comment
Read more
  The Guardrails of Automation VMware Cloud Foundation (VCF) 9.0 has redefined private cloud automation. With full-stack automation powered by Ansible and orchestrated through vRealize Orchestrator (vRO), and version-controlled deployments driven by GitOps and CI/CD pipelines, teams can build infrastructure faster than ever. But automation without guardrails is a recipe for risk Enter RBAC and policy enforcement. This third and final installment in our automation series focuses on how to secure and govern multi-tenant environments in VCF 9.0 with role-based access control (RBAC) and layered identity management. VCF’s IAM Foundation VCF 9.x integrates tightly with enterprise identity providers, enabling organizations to define and assign roles using existing Active Directory (AD) groups. With its persona-based access model, administrators can enforce strict boundaries across compute, storage, and networking resources: Personas : Global Admin, Tenant Admin, Contributor, Viewer Projec...
Post a Comment
Read more