Skip to main content
NetApp Knowledge Base

SCV upgrade to 4.8 fails to upgrade dotnet runtime files

Views:
4,111
Visibility:
Public
Votes:
5
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Plug-in for VMware vSphere (SCV) 4.8

Issue

  • SCV upgrade to 4.8 is shown as successful in the maintenance console
  • SCV, when upgrading from a version earlier than 4.7 (since 4.7 already has the newer dotnet), will complain:

Failed to get protection services status from configuration service: Connection refused (Connection refused). Please make sure the protection services are up and running

  • Though daemon.log reveals errors:

Jan 31 14:46:15 mbrscv systemd[1]: Starting protection rbac service...
Jan 31 14:46:15 mbrscv protectionservice-rbac[14936]: It was not possible to find any compatible framework version
Jan 31 14:46:15 mbrscv protectionservice-rbac[14936]: The framework 'Microsoft.NETCore.App', version '6.0.0' was not found.
Jan 31 14:46:15 mbrscv protectionservice-rbac[14936]:   - The following frameworks were found:
Jan 31 14:46:15 mbrscv protectionservice-rbac[14936]:       3.1.2 at [/usr/bin/dotnet/shared/Microsoft.NETCore.App]
Jan 31 14:46:15 mbrscv protectionservice-rbac[14936]: You can resolve the problem by installing the specified framework and/or SDK.
Jan 31 14:46:15 mbrscv protectionservice-rbac[14936]: The specified framework can be found at:
Jan 31 14:46:15 mbrscv protectionservice-rbac[14936]:   - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=debian.11-x64
Jan 31 14:46:30 mbrscv protectionservice-rbac[14926]: /
Jan 31 14:46:30 mbrscv systemd[1]: protectionservice-rbac.service: New main PID 14936 does not exist or is a zombie.
Jan 31 14:46:30 mbrscv systemd[1]: protectionservice-rbac.service: Failed with result 'protocol'.

  • The SCV plug-in UI is not populated and when try to restart the SCV services, maintenance console errors displayed:

Job for the protectionservice-rbac.service failed because the service did not take the steps required by its unit configuration.
A dependency job for the scvservice.service failed. See journalctl -xe for details.
A dependency job for the protectionservice-backup.service failed. See journalctl -xe for details.
A dependency job for the protectionservice-configuration.service failed. See journalctl -xe for details.
A dependency job for the protectionservice-job.service failed. See journalctl -xe for details.
A dependency job for the protectionservice-logger.service failed. See journalctl -xe for details.
A dependency job for the protectionservice-policy.service failed. See journalctl -xe for details.
A dependency job for the protectionservice-report.service failed. See journalctl -xe for details.
A dependency job for the protectionservice-resources.service failed. See journalctl -xe for details.
A dependency job for the protectionservice-scheduler.service failed. See journalctl -xe for details.
A dependency job for the protectionservice-storage.service failed. See journalctl -xe for details.

Failed to VMware plugin status: Connection refused (Connection refused). Please make sure the plugin is up and running. Failed to get protection services status from configuration service. Connection refused (Connection refused). Please make sure the protection services are up and running.

vCenter Plugin connection has failed. VADP Server error occurred

 

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.