"vSAN Build Recommendation - vSAN release catalog up-to-date" alarm occurs only after vCenter Server restart.
search cancel

"vSAN Build Recommendation - vSAN release catalog up-to-date" alarm occurs only after vCenter Server restart.

book

Article ID: 426672

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSAN

Issue/Introduction

  • "vSAN Build Recommendation - vSAN release catalog up-to-date" alarm occurs only after vCenter Server restart.
  • The alarm does not occur while the vCenter Server is running.
  • The vSphere Lifecycle Manager (vmware-updatemgr) service stopped.
     Username@Hostname [/]# service-control --status vmware-updatemgr
     Stopped:
     vmware-updatemgr

Environment

VMware vCenter Server

VMware vSAN

Cause

If vSphere Lifecycle Manager stopped, "vSAN Build Recommendation - vSAN release catalog up-to-date" is not checked. 
However, even if vSphere Lifecycle Manager stopped, the check is performed only when the vCenter Server is restarted.
Therefore, if the release catalog is actually out of date, the alarm will only occur after rebooting vCenter Server.

Resolution

If you don't use vSphere Lifecycle Manager, you can ignore the alarm.
To prevent the alarm from being output even after the reboot, update the release catalog by the following article.
vSAN Skyline Health - vSAN Build Recommendation - vSAN release catalog up-to-date