Upgrading vRealize Identity manager 3.3.2 to 3.3.4 fails on Inventory Sync stage with error LCMVCF19115

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Starting from VCF Version 4.1 onward, upgrading the vIDM is done from the VMware Aria Suite Lifecycle.
• After initiating vIDM upgrade, an issue is encountered after triggering an Inventory sync, which is part of the Upgrade workflow. 
  
• Instead of receiving "Completed" banner and enabling the "Proceed" button, we see the following error:
  
  
  
  
  
• Expanding the log via the Show more... button, we see the following log:
  com.vmware.vrealize.lcm.plugin.vcf.common.exception.PollValidateProductRegistrationException: All retries exhausted. Could not get validation product registration status. at com.vmware.vrealize.lcm.vcf.plugin.tasks.PollValidateProductRegistrationTask.execute(PollValidateProductRegistrationTask.java:141) at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:45) 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)
• Since every component is healthy, you have the option to Retry the inventory sync as pointed out above. Upon retrying, the process will always complete with success, however the upgrade will not proceed as the flow is already broken. Therefore, skipping this step is not possible from UI perspective. When starting a new upgrade, this situation is looped and the same failure is expected with identical behavior.

Environment

VMware Identity Manager 3.3.x

VMware Aria Suite Lifecycle 8.x

Cause

SDDC logs should point out a delay when registering WS1A(Workspace One/Identity manager)  VMs in SDDC Manager. SSH connection from SDDC to one of the IDM VMs was tested and a latency was observed until full SSH login to OS completes (up to 1 min). This is the reason the automation timeouts.

Resolution

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