vCenter is displaying "vLCM Image Recommendation Generation Alarm" alert on vCenter

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, you get these duplicate exceptions.

Resolution

1. Take a Snapshot of the vCenter VM
2. SSH into the VCSA as root, connect to the DB
   
   

   /opt/vmware/vpostgres/current/bin/psql -U postgres VCDB

3. Find the Duplicate Alarm
   
   

   SELECT alarm_id, name FROM vpx_alarm WHERE name LIKE '%vLCM Image Recommendation Generation Alarm%';

4. Delete the Duplicate alarm from the DB
   
   

   DELETE FROM vpx_alarm_expression WHERE alarm_id = <DUPLICATE_ID>;
   DELETE FROM vpx_alarm WHERE alarm_id = <DUPLICATE ID>;
   

   Note: Copy the duplicate ID from step 3

5. After the Cleanup, restart the vCenter Services
   
   

   service-control --stop --all
   service-control --start --all
   

   This will remove the duplicate definition from the DB and stop the vim.fault.DuplicateName errors.