After powering off the VM goes in "Inconsistent Status" and cannot be powered on again
search cancel

After powering off the VM goes in "Inconsistent Status" and cannot be powered on again

book

Article ID: 421502

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • vApp/VMs are in inconsistent state on VMware Cloud Director and does not connect nic to portgroup att power on vm
  • Once powering off the VM from Cloud Director UI, you are not longer able to power the VM on
  • from the Cloud Director debug logs you will get the following error :

[Activity Execution] Uncaught Exception during Activity execution. Recent phase: com.vmware.ssdc.backend.DeployVmOnFabricsActivity$DeployVMsComputeFabricPhase@###### - Handle: urn:uuid:########-####-####-####-###########, Current Phase: DeployVmOnFabricsActivity$DeployVMsComputeFabricPhase | activity=(com.vmware.vcloud.vimproxy.internal.impl.PCEventProcessingActivity,urn:uuid:########-####-####-####-###########) activity=(com.vmware.ssdc.backend.ReactToVmPowerStateChangeInVcActivity,urn:uuid:########-####-####-####-###########) vcd=########-####-####-####-###########,task=########-####-####-####-########### activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:########-####-####-####-###########) activity=(com.vmware.ssdc.backend.DeployVAppVmSubsetActivity,urn:uuid:########-####-####-####-###########) activity=(com.vmware.ssdc.backend.DeployVmOnFabricsActivity,urn:uuid:########-####-####-####-###########)
java.util.concurrent.ExecutionException: java.lang.NullPointerException
        at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:136)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.NullPointerException
        at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool.findAllowedComputeOnPvdcRP(GenericVirtualResourcePool.java:729)
        at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool.computeResourcePoolConfig(GenericVirtualResourcePool.java:2157)
        at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool.computeAndAdjustDelta(GenericVirtualResourcePool.java:4458)
        at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool.deployAdmittedVms(GenericVirtualResourcePool.java:3397)
        at com.vmware.vcloud.fabric.compute.vrp.GenericVirtualResourcePool.deployVms(GenericVirtualResourcePool.java:496)
        at com.vmware.vcloud.fabric.compute.impl.ComputeFabricImpl.deployVms(ComputeFabricImpl.java:356)
        at jdk.internal.reflect.GeneratedMethodAccessor22530.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:234)
        at com.sun.proxy.$Proxy273.deployVms(Unknown Source)
        at com.vmware.ssdc.backend.DeployVmOnFabricsActivity$DeployVMsComputeFabricPhase.invoke(DeployVmOnFabricsActivity.java:156)
        at com.vmware.vcloud.activity.executors.ActivityRunner.runPhase(ActivityRunner.java:175)
        at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:112)
        ... 5 more

Environment

VMware Cloud Director 10.6.1.1

Cause

This issue is caused by the presence of an invalid resource pool entry associated with an Organization VDC (OrgVDC).

Resolution

To work around this issue, contact Broadcom Support and note this Article ID (421502) in the problem description. For more information, see Creating and managing Broadcom support cases.