Skip to main content
NetApp Knowledge Base

Added storage's 'Operation Status' never becomes 'completed' and its name or status is not shown on AIQUM Cluster Setup page

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

Applies to

ActiveIQ Unified Manager (AIQUM)

Issue

  • On AIQUM Cluster Setup page, new storage was added,  but its Operation State does not become Completed.
  • Some fields like name, status, etc.. are shown as blank.
  • OCUMSERVER log includes the following error.

2023-06-02 02:32:34,375 ERROR [oncommand] [job-326] [refresh(dataSource=XX.XX.XX.XX)|forceAcquisition] [com.netapp.dfm.job.JobEngine] Error executing job <JOB ID>: Timed out after 02:00:00 while waiting on acquisition forced at 00:32:34.361
java.lang.RuntimeException: Timed out after 02:00:00 while waiting on acquisition forced at 00:32:34.361
    at deployment.dfm-app.war//com.netapp.dfm.collector.InventoryChangeWaitTask.suspendIfNecessary(InventoryChangeWaitTask.java:201)
    at deployment.dfm-app.war//com.netapp.dfm.collector.InventoryChangeWaitTask.resume(InventoryChangeWaitTask.java:148)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at deployment.dfm-app.war//com.netapp.dfm.job.TaskExecuteInvocation.invoke(TaskExecuteInvocation.java:37)
    at deployment.dfm-app.war//com.netapp.dfm.job.JobEngine.executeTask(JobEngine.java:543)
    at deployment.dfm-app.war//com.netapp.dfm.job.JobEngine.process(JobEngine.java:513)
    at deployment.dfm-app.war//com.netapp.dfm.job.JobEngine.process(JobEngine.java:56)
    at deployment.dfm-app.war//com.netapp.dfm.job.JobEngine$$FastClassBySpringCGLIB$$4bdbd68e.invoke(<generated>)
    at deployment.dfm-app.war//org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218)
    at deployment.dfm-app.war//org.springframework.aop.framework.CglibAopProxy.invokeMethod(CglibAopProxy.java:386)
    at deployment.dfm-app.war//org.springframework.aop.framework.CglibAopProxy.access$000(CglibAopProxy.java:85)
    at deployment.dfm-app.war//org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:704)
    at deployment.dfm-app.war//com.netapp.dfm.job.JobEngine$$EnhancerBySpringCGLIB$$82170e35.process(<generated>)
    at deployment.dfm-app.war//com.netapp.dfm.workqueue.WorkerThread.run(WorkerThread.java:44)

 

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.