Skip to main content
NetApp Knowledge Base

CAIQUM-8548: Polling of CVOs fails due to efficiency state missing from API response for DP destination volumes

Views:
2
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
om
Last Updated:

Issue

  • Monitoring of CVOs within Unified Manager fail
  • Error seen in the AU.log


2025-12-05 11:40:56,720 ERROR [common-pool-0] c.o.s.a.f.d.BaseDataSource (BaseDataSource.java:336) - [netappfoundation] <cluster name here> - Runtime exception: null java.lang.NullPointerException
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.transform.ocie.NetAppOCIETransform.transformVolumeSisStatus(NetAppOCIETransform.java:2077) ~[au-datasource-netappfoundation.jar:9.16.0-2025.05.J22]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.transform.ocie.NetAppOCIETransform.transform(NetAppOCIETransform.java:199) ~[au-datasource-netappfoundation.jar:9.16.0-2025.05.J22]
    at com.onaro.sanscreen.acquisition.datasource.netapp_ocie.NetAppOCIEDataSource.doFoundation(NetAppOCIEDataSource.java:300) ~[au-datasource-netappfoundation.jar:9.16.0-2025.05.J22]
    at com.onaro.sanscreen.acquisition.netappfoundation.datasource.NetAppFoundationPackage.pollNow(NetAppFoundationPackage.java:199) ~[au-package-netappfoundation.jar:9.16.0-2025.05.J22]
    at com.onaro.sanscreen.acquisition.framework.datasource.BaseDataSource.run(BaseDataSource.java:269) ~[au-framework.jar:9.16.0-2025.05.J22]
    at com.onaro.sanscreen.acquisition.framework.mgmt.DataSourceManager$PollLogic.run(DataSourceManager.java:756) ~[au-framework.jar:9.16.0-2025.05.J22]
    at com.onaro.sanscreen.acquisition.framework.mgmt.scheduler.SchedulerTask.runLogic(SchedulerTask.java:102) ~[au-framework.jar:9.16.0-2025.05.J22]
    at com.onaro.sanscreen.acquisition.framework.mgmt.scheduler.Scheduler$LogicWrapper.run(Scheduler.java:271) ~[au-framework.jar:9.16.0-2025.05.J22]
    at com.onaro.commons.metrics.executor.ThreadPoolMonitorExecutor.lambda$submit$1(ThreadPoolMonitorExecutor.java:178) ~[commons-commons.jar:9.16.0-2025.05.J22]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
    at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
    at com.onaro.commons.metrics.executor.ThreadPoolMonitorExecutor.lambda$execute$0(ThreadPoolMonitorExecutor.java:164) ~[commons-commons.jar:9.16.0-2025.05.J22]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
    at java.lang.Thread.run(Thread.java:829) ~[?:?]

 

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.