Lifecycle manager scaleout of vIDM failed with Error Code LCMCOMMON80084

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Lifecycle Manager scale out of vIDM fails to delete snapshots at stage 21 of 23.

• The /var/log/vrlcm/vmware_vrlcm.log may contain the following message.

INFO vrlcm[1132] [] [c.v.v.l.r.c.RequestController]  -- Retry error cause data : [ {
  "messageId" : "LCMCOMMON80084",
  "message" : "Failed to find the vMoid. Perform the inventory sync and make sure that Virtual Machines are located under the cluster in vCenter. Refer to VMware Aria Suite Lifecycle logs for additional details and retry.",
  "eventId" : "#######-####-####-####-##########",
  "retry" : true,
  "exceptionMessage" : "Unable to find vnid for node->   from product-> ",
  "exceptionStackTrace" : "com.vmware.vrealize.lcm.drivers.commonplugin.exceptions.NodeVmidException: Unable to find vnid for node->   from product-> \n\tat com.vmware.vrealize.lcm.drivers.commonplugin.task.GetVmidDeleteSnapShotTask.execute(GetVmidDeleteSnapShotTask.java:96)\n\tat com.vmware.vrealize.lcm.drivers.commonplugin.task.GetVmidDeleteSnapShotTask.retry(GetVmidDeleteSnapShotTask.java:143)\n\tat com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:60)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\tat java.base/java.lang.Thread.run(Unknown Source)\n",
  "localizedMessageId" : null,
  "parameters" : null,
  "properties" : { }

Environment

VMware Identity Manager 3.3.7

Resolution

• No resolution at this time.

Workaround:

• Follow the steps below if and only if the scale-out has reached stage 21 of 23, which is to delete the snapshot taken of the existing vIDM node prior to adding the additional nodes.
• Manually delete the snapshot in vCenter.
• Perform an Inventory Sync of vIDM in Lifecycle Manager, this action is the same as if the remaining two stages of the scale-out completed.
• The vIDM cluster is now ready for use.