Deploying or enabling multitenancy returns a LCMVIDM71043 error when updating vIDM FQDN

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• When deploying a vIDM cluster or when enabling multi-tenancy from Aria Lifecycle Manager, there is LCMVIDM71043 error during configuring vIDM FQDN.
  
  
• On Aria Lifecycle Manager, in /var/log/vrlcm/vmware_vrlcm.log, there is error as below:
  
  yyyy-mm-ddThh:mm:ss.sss+00:00 INFO vrlcm[xxxx] [pool-x-thread-xx] [c.v.v.l.p.a.s.Task]  -- Injecting task failure event. Error Code : 'LCMVIDM71043', Retry : 'true', Causing Properties : '{ CAUSE :: vidmLBHostname === hostName === vidmSystemAdminPassword YXYXYXYX  }'
com.vmware.vrealize.lcm.common.exception.LcmException: Error while validate FQDN for VIDM:vidm.domain.name, Message: {"message":"Error validating Identity Manager url.","code":2,"success":false,"results":null,"resultObj":null,"fieldMessages":null,"redirectUrl":null}
        at com.vmware.vrealize.lcm.vidm.driver.helpers.VidmInstallHelper.invokeVidmFQDNApi(VidmInstallHelper.java:580) ~[vmlcm-vidmplugin-driver-8.18.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.vidm.driver.helpers.VidmInstallHelper.changeFQDNForVidm337AndAbove(VidmInstallHelper.java:523) ~[vmlcm-vidmplugin-driver-8.18.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.vidm.driver.helpers.VidmInstallHelper.changeFQDN(VidmInstallHelper.java:513) ~[vmlcm-vidmplugin-driver-8.18.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.vidm.core.task.VidmFQDNUpdateTask.execute(VidmFQDNUpdateTask.java:115) [vmlcm-vidmplugin-core-8.18.0-SNAPSHOT.jar!/:?]
        at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:62) [vmlcm-engineservice-core-8.18.0-SNAPSHOT.jar!/:?]
        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

Aria Lifecycle Manager 8.18

Identity Manager 3.3.7

Cause

On affected vIDM, the content in /usr/local/horizon/conf/system-config.properties is not listed in a proper sequence.

Resolution

1. Take a snapshot of the affected vIDM node.
   
   
2. Stop the horizon workspace service on the affected node using the command:
   service horizon-workspace stop
   
   
3. Check the content of file /usr/local/horizon/conf/system-config.properties of the affected node.
   Make sure the content is strictly in same sequence as below from top to bottom:
   
   ClientID=Configurator_OAuthClient
suiteToken=XXXXX
tenant.id=XXXXXX
application.initialized=true


4. Restart the horizon service on the affected node using the command:
   service horizon-workspace restart


5. Perform an Inventory Sync of vIDM in Aria Lifecycle before retrying the failed task in Aria Lifecycle.