"No healthy upstream" error when accessing the Images section under the Updates tab in vCenter Server
search cancel

"No healthy upstream" error when accessing the Images section under the Updates tab in vCenter Server

book

Article ID: 415163

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • Below error message is displayed when accessing the Images section under the Updates tab in vCenter:

  • Lifecycle manager option may be missing from the vCenter Server main menu.

  • The vmware-updatemgr service will be in a STOPPED state after a vCenter reboot or service restart which can be verified using the following command: service-control --status --all

  • Manual starts of the vmware-updatemgr service using the following command resolves the issue temporarily, but it does not persist after a reboot : service-control --start vmware-updatemgr

  • In /var/log/vmware/vmon/vmon.log, Below message can be seen :

Er(02) host-##### Startup type of service rbd is AUTOMATIC while startup type of dependent service updatemgr is MANUAL.

Environment

VMware vCenter Server 8.X

VMware vCenter Server 7.X

Cause

The startup type for the vmware-updatemgr service is set to MANUAL instead of AUTOMATIC.

Resolution

  1. Execute the following command to verify the startup type and compare the results with the sample output below :

    # vmon-cli -s updatemgr

    Name: updatemgr
    Starttype: MANUAL
    RunState: STOPPED
    RunAsUser: updatemgr
    CurrentRunStateDuration(ms): #########
    HealthState: UNHEALTHY
    FailStop: FALSE

    MainProcessId: N/A

  2. Set the service to start automatically after the vCenter reboot using below command:

    vmon-cli -U updatemgr -S AUTOMATIC

  3. Start vmware-updatemgr service:

    service-control --start vmware-updatemgr