Skip to main content
NetApp Knowledge Base

CVO status showing as failed in BlueXP

  1. Last updated
  2. Save as PDF
Views:
47
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
netapp_console
Last Updated:

Applies to

  • BlueXP
  • Cloud Volumes ONTAP (CVO)
  • Microsoft Azure

Issue

  • After upgrade of BlueXP to 3.9.53, CVO may show as failed
  • Error messages from Server.log
    (oncloud-akka.actor.default-dispatcher-2615) [StatusUpdaterActor:182] Done update status for Working Environment <cluster_name>. status=FAILED, license type=capacity, . update status results=Some(StatusReportExtended(VsaWorkingEnvironment-xxxxxxxx,FAILED,capacity,Some(Map(ALLOCATED_CAPACITY_GB -> 0)),Some(<ID>),Some(List())))
    (oncloud-akka.actor.default-dispatcher-2611) [AzureConfigService:416] Marketplace version and sku for working environment <cluster_name> were not found because a deployment with name <cluster_name>deployment not found. Continue without

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.