NO_FEASIBLE_PLACEMENT_SOLUTION while moving a live vAPP using API or VMware NSX Migration for VMware Cloud Director tool

Products

• VMware Cloud Director

Issue/Introduction

• while moving a live VM using API or NSXV-T Migration tool user get error "NO_FEASIBLE_PLACEMENT_SOLUTION"
  
  
  
  
• While investigating logs from vcd (vcloud-container-debug.log) we can see following stack:

Rejecting host [vcId=XXXXXX, moref=host-XX] because a network change is required (new target network: XXXXl) and the VM is currently residing on the host

 

Environment

VMware Cloud Director 10.3.3

Cause

• HostLevelPlacementFinder is rejecting a host because there is a network change involved
• Beside the host where VM resides there are no more hosts available inside the hub
• Network placement fails because there are no hubs available after the only host is filtered out
• The network placement of powered-on VMs require at least two hosts.

Resolution

• Add more hosts to the cluster or power off VM 

Additional Information

• The official process and requirements to move a VM using the UI can be seen here

Notes:

• When a change of network occurs the VM must be on a powered off state
• While using API it is possible to overcome this limitation however you will need always to have at least 2 hosts to be able to keep the VM live and workable while its being created on the new host/cluster/resource pool
• VMware NSX Migration for VMware Cloud Director tool is no longer supported as it can be seen here
• There are multiple issues related with error "NO_FEASIBLE_PLACEMENT_SOLUTION" so make sure the logs match with all conditions from "Issue/Introduction"