Skip to main content
NetApp Knowledge Base

SCV fails to load the dashboard with the message "no healthy upstream"

Views:
934
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:
5/8/2024, 4:31:25 PM

Applies to

  • SnapCenter Plug-in for VMware vSphere (SCV)
  • ONTAP Tools for VMware vSphere (OTV)

Issue

Fails to load the SCV dasboard with message no healthy upstream

 SCV:

https://192.168.0.10:8080/scv/plugin.json in vCenter vcenter_name, for object vCenter (9b784162-a0e2-4128-9502-eb24c271edcf) with servers [url = https://192.168.0.10:8080/scv/plugin.json,type = MANIFEST_SERVER,thumbprint = 61:bb:17:de:c8:1e:d1:c3:76:a3:d5:69:5a:59:b9:78:7f:a9:de:92,certificate = null]. 
 
[INFO ] http-nio-5090-exec-153       70040012 101208 200077 com.vmware.vise.mvc.controllers.PluginServiceController           Fetching session for remote plugin with ref com.netapp.scv.client:4.9.0.6245912:-1032673542 
[2023-12-11T13:21:37.254+05:30] [ERROR] ata-notifications-worker-376  com.vmware.vise.mvc.notifications.UpdateNotificationProvider      Could not get extension info:  com.vmware.vapi.std.errors.Error: Error (com.vmware.vapi.std.errors.error) => {
    messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = com.vmware.vcenter.vlcm.depotmanager.repository_not_reachable.error,
    defaultMessage = Configured repository is not accessible due to network connectivity or incorrect URL.,
    args = [],
    params = <null>,
    localized = Configured repository is not accessible due to network connectivity or incorrect URL.
}, LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = com.vmware.vcenter.vlcm.depotmanager.repository_not_reachable.resolution,
    defaultMessage = Verify the repository settings.,
    args = [],
    params = <null>,
    localized = Verify the repository settings.
}],
    data = <null>,
    errorType = ERROR
}
 

 

ONTAP tools for VMware vSphere:

[ERROR] http-nio-5090-exec-209       70052860 101158 200075 com.vmware.vise.mvc.controllers.PluginServiceController           Plugin Server dynamic uri endpoint 'https://vcenter_name/plugins/com.netapp.vsch5~9.12.0.34780~-244424531/192.168.0.10-8443//rest/services/vcenter-extensions/vm/actions' returned an error: no healthy upstream 
[2023-12-11T19:20:12.871+05:30] [ERROR] ata-notifications-worker-389  com.vmware.vise.mvc.notifications.UpdateNotificationProvider      Could not get extension info:  com.vmware.vapi.std.errors.Error: Error (com.vmware.vapi.std.errors.error) => {
    messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = com.vmware.vcenter.vlcm.depotmanager.repository_not_reachable.error,
    defaultMessage = Configured repository is not accessible due to network connectivity or incorrect URL.,
    args = [],
    params = <null>,
    localized = Configured repository is not accessible due to network connectivity or incorrect URL.
}, LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
    id = com.vmware.vcenter.vlcm.depotmanager.repository_not_reachable.resolution,
    defaultMessage = Verify the repository settings.,
    args = [],
    params = <null>,
    localized = Verify the repository settings.
}],
    data = <null>,
    errorType = ERROR
}

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.