Move deployment to another project* Failed

Products

• VCF Automation

Issue/Introduction

In Service Broker if you select Deployments > select a specific Deployment > Actions > Change Project > Selected Project you may encounter the error next to the deployment name:
"Move deployment to another project* Failed":

 

Environment

Aria Automation 8.18.x

Cause

This issue is caused by manual changes being made to the underlying deployment resources outside of the Aria Automation, usually via the vCenter UI or API.

As a result there is a discrepancy between the up-to-date metadata for the resource in vCenter and an outdated version recorded in the Aria Automation database.

Resolution

Workaround:

Unregister and re-onboard the desired Virtual Machine:

• Take snapshots of the Aria Automation environment as well as full backups of the appliances and Database.
• Unregister the VM from the Deployment:
  • Go to Service Broker > Consume > Deployments > Selected Deployment > Selected Virtual Machine > Actions >  Unregister.
  • 

 

• Re-onboard the VM to a new Deployment after waiting up to 10 minutes for Inventory Sync.
  • Go to Service Broker > Consumer > Deployments > Virtual Machines > Discovered > Tick checkbox next to Selected VM > Onboard:
  • 

 

• Make sure to add the new desired Project here to avoid having to "Change Project" again.