In VMware vCenter, under the Updates tab for a specific cluster, the message "No healthy upstream" is displayed. This issue prevents vCenter from displaying update status or managing update configurations for the cluster. Users may experience difficulties in initiating or applying updates for ESXi hosts within the affected cluster.
This can be due any of the below reasons :
1. Network connectivity issues: vCenter may not be able to connect to the update source due to firewall restrictions, DNS issues, or network misconfigurations.
2. Proxy server misconfiguration: If a proxy server is required to access external resources, incorrect proxy settings can lead to failed connections to the VMware update repository.
3. vSphere Lifecycle Manager (vLCM) issues: vLCM may not be able to communicate properly with the update servers or the update server itself may be unresponsive or experiencing downtime.
Initially all the above should be validated.
VMware vCenter Server 7.x
VMware vCenter Server 8.x
The "No healthy upstream" message typically occurs when there is a connectivity issue between vCenter Server and the update sources (usually the VMware patch repository or internal update servers). This issue can be caused by:
Typically a Lifecycle Manager backend service hang or DB connectivity loss.
Restart of all the vCenter services at once fixed the issue.
1. Login to vCenter putty using root credentials.
2. To restart all the services on the vCenter use the below command :
service-control --stop --all && service-control --start --all