OVF deployment fails with error "A component of the virtual machine is not accessible on the host." when the Cluster is selected for the deployment.
search cancel

OVF deployment fails with error "A component of the virtual machine is not accessible on the host." when the Cluster is selected for the deployment.

book

Article ID: 422815

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

  • OVF deployed only at the Cluster level fails with error "A component of the virtual machine is not accessible on the host."
  • OVF deployment succeeds if a specific host is selected during the deployment. 
  • VPXD logs highlight the error - /var/log/vmware/vpxd/vpxd.log 

    DD-MM-YYYY info vpxd[26041] [Originator@6876 sub=VAppImport opID=6413d8c1-01-01] Exception during CreateVM: N3Vim5Fault23CannotAccessVmComponent9ExceptionE(Fault cause: vim.fault.CannotAccessVmComponent
    --> )
    --> [context]zKq7AVECAQAAAI48ewEednB4ZAAAQxxTbGlidm1hY29yZS5zbwAACBhCACk/QwCWmUqBU0U6AWxpYnZpbS10eXBlcy5zbwCBfmM6AYEsZDoBgfxlOgGC3DgjAXZweGQAgiMxNQKC/Us1AoLa+z0CgvkXNQKCWatHAYJceYECgqeJgQKCm5yAAoKA+oACggyqRwGCVc5HAYKT0kcBglx5gQKCp4mBAoKbnIACgopzgQIABOw3ABdFOADFD1EDsI4AbGlicHRocmVhZC5zby4wAATf+g9saWJjLnNvLjYA[/context]
    DD-MM-YYYY info vpxd[26041] [Originator@6876 sub=vpxLro opID=6413d8c1-01-01] [VpxLRO] -- FINISH lro-10508356
    DD-MM-YYYY error vpxd[26041] [Originator@6876 sub=Default opID=6413d8c1-01-01] [VpxLRO] -- ERROR lro-10508356 --  --  -- ResourcePool.ImportVAppLRO: :vim.fault.CannotAccessVmComponent
    --> Result:
    --> (vim.fault.CannotAccessVmComponent) {
    -->    faultCause = (vmodl.MethodFault) null,
    -->    faultMessage = (vmodl.LocalizableMessage) [
    -->       (vmodl.LocalizableMessage) {
    -->          key = "com.vmware.vim.vm.error.NoValidHostDueToDasState",
    -->          arg = <unset>,
    -->          message = <unset>
    -->       }
  • Cluster is only a 2 node cluster. 

Environment

VMware vCenter Server 
VMware vSphere ESXi 

Cause

The error is encountered due to HA Admission Control Policy of the cluster. The cluster has 2 hosts and both of them set as dedicated failover hosts. By design, to ensure that spare capacity is available on a failover host, you are prevented from creating virtual machines, powering on virtual machines or using vMotion to migrate virtual machines to a failover host.

Resolution

Change the HA Admission Control Policy to Cluster Resources Percentage Admission Control. For details regarding the Cluster Resources Percentage Admission Control, refer - Cluster Resources Percentage Admission Control
1. Log in to vCenter Server with vSphere Client as an administrator.
2. Right-click the Cluster in the Inventory and click Settings.
3. Click vSphere Availability > Edit > Admission Control > Define host failover capacity by 
4. Select the Cluster Resource Percentage