Skip to main content
NetApp Knowledge Base

CVO going to failed state frequently in NetApp Console

  1. Last updated
  2. Save as PDF
Views:
340
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
netapp_console
Last Updated:

Applies to

  • NetApp Console (BlueXP)
  • RHEL / Podman
  • Memory issue with OCCM container

Issue

  • CVO discovered in NetApp console keep going in failed state intermittently.
  • All CVO working environments in console canvas are reported as failed with the error below:
    akka.pattern.AskTimeoutException: Recipient[Actor[akka://oncloud/user/ConfigurationActor#1412321233]] had already been terminated. Sender[null] sent the message of type "com.netapp.oncloud.common.configuration.ConfigActor$GetValue"
  • NetApp console agent reboot or service-manager restart does not fix the issue permanently as the working environments are marked again as failed after sometime following the restart

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.