• LCMCOMMON80005 No VM found in the vCenter with HostName and morefID error when extending Aria Suite Lifecycle storage.
• The /var/log/vrlcm/vmware_vrlcm.log contains a stack trace similar to:

com.vmware.vrealize.lcm.common.exception.userinput.VirtualMachineNotFoundException: No VM found in the vCenter with HostName : <AriaSuiteLifecycleFQDN> and morefID : vm-<Integer> at com.vmware.vrealize.lcm.drivers.vsphere65.vlsi.guest.VsphereDiskManager.expandExistingDiskOfVM(VsphereDiskManager.java:67) at com.vmware.vrealize.lcm.plugin.lcmplugin.core.task.LcmVaExtendDiskTask.execute(LcmVaExtendDiskTask.java:96) at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:62) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source)

•  The issue typically occurs after restoring Aria Suite Lifecycle from backup or migrating to a different vCenter
•  The Aria Suite Lifecycle appliance's moref id in vCenter differs from whats stored in its own filesystem. The moref id is stored as the vCenterId in the file /opt/vmware/etc/vami/ovfEnv.xml on the Aria Suite Lifecycle appliance. To check the moref id in vCenter you can use the vCenter mob or you can browse to the Aria Sutie lifecycle appliance in the vSphere client and check the moref in the browser url:

To resolve the issue correct the stale moref entry in the /opt/vmware/etc/vami/ovfEnv.xml file:

1. Snapshot the Aria Suite Lifecycle appliance.
2. Confirm the correct moref id of the Aria Suite Lifecycle appliance in vCenter. You can check the mob using procedure outlined in KB 1017126 or browse to the Aria Suite lifecycle appliance in the vSphere client and check the moref in the browser url:

3. Open the /opt/vmware/etc/vami/ovfEnv.xml file in a text editor and change the vCenterId value to match the moref id documented step 2:

vi /opt/vmware/etc/vami/ovfEnv.xml

To exit the text editor and save the changes type:

:wq!

4. Test again the failing operation, it should now succeed.