Inventory Sync of VMware Identity Manager Services fails with error code LCMVIDMIMPORT0019 in Aria Suite Lifecycle Manager
search cancel

Inventory Sync of VMware Identity Manager Services fails with error code LCMVIDMIMPORT0019 in Aria Suite Lifecycle Manager

book

Article ID: 370305

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Following a change in the default domain tenant address of vIDM, attempts to do an inventory sync result in error code LCMVIDMIMPORT0019.

Here is an example of the error encountered:

When triggering an inventory sync of vIDM from vLCM, the following error occurs:

com.vmware.vrealize.lcm.common.exception.LcmException: Failed to get admin token: 
	at com.vmware.vrealize.lcm.vidm.driver.rest.util.VidmServerRestUtil.loginLocalAdmin(VidmServerRestUtil.java:240)
	at com.vmware.vrealize.lcm.vidm.driver.helpers.VidmImportUtil.getPostInstallDetails(VidmImportUtil.java:271)
	at com.vmware.vrealize.lcm.vidm.core.task.VidmPostImportEnvironmentTask.execute(VidmPostImportEnvironmentTask.java:101)
	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)

 

Environment

vIDM 3.3.x

Resolution

In order to resolve this follow the below steps :

Ensure you have a snapshot of the vIDM appliance before proceeding.

For Single-node vIDM 3.3.x:

  • Verify the entries in runtime-config.properties(navigate to /usr/local/horizon/conf) to ensure gateway.hostname and configurator.hostname are same.

gateway.hostname= <Node-FQDN>
gateway.port=443
configurator.hostname= <Node-FQDN>
configurator.port=443

For cluster-vIDM 3.3.x:

  • Verify the entries in runtime-config.properties(navigate to /usr/local/horizon/conf):
    • Set gateway.hostname to the Load-Balancer FQDN.
    • Set configurator.hostname to the FQDN of the individual node

gateway.hostname=<Load-Balancer-FQDN>
gateway.port=443
configurator.hostname=<Individual-Node-FQDN>
configurator.port=443

These adjustments ensure correct configuration settings, which should help resolve the issue.