vCenter is displaying "vLCM Image Recommendation Generation Alarm" alert on a vSphere cluster

Products

• VMware vCenter Server

Issue/Introduction

• vCenter Cluster shows the following alert after vCenter is upgraded to 8.x.
   
  vLCM Image Recommendation Generation Alarm
  
  
• Acknowledging/disabling the alarm doesn't help as it keeps triggering again.
• /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log of vCenter shows "DuplicateName exception" for the same alarm.
  
  

  ##:##:####:###z info vmware-vum-server[###] [Originator@6876 sub=vmomi. soapStub[0]]( SOAP request returned HTTP failure; /Sdk>, method: create; code: 500(Internal Server Error); fault: (vim.fault.DuplicateName) { 
-->faultCause = (vmodl.MethodFautt) null, 
-->faultMessage = <unset>, 
-->name = "vLCM Image Recommendation Generation Alarm", 
-->object = 'vim.alarm.Alarm: #####:alarm- ###

  -->msg "Received SOAP response fault from p:0x0007f0raeebfba0, h:20, <TCP • 127.0.0.1 : 40426'>. <TCP '127.0.0.1 : /Sdk>I: create 
-->The name 'vLCM Image Recommendation Generation Alarm' already exists. " 
##:##:#####:##z: error [Originator@6876:ReUtil  902]RegisterVcAlarmIfNeeded: Error occurred when checking/registering VC alarm for cluster domain- ##
Error: Dynamic exception type:Vim:Fault::DuplicateName::Exception
-->std:exception::what ::Fault Cause: vim. fault.DuplicateName 
-->

  
  

Environment

VMware vCenter Server 8.x

Cause

The upgrade process attempts to create new system alarms, but if they already exist in vCenter’s database it can lead to this duplicate exceptions and alarm triggering.

Resolution

If you believe you have encountered this issue, open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.