ViPR Controller: Fabric Manager discovery fails with "The discovery for this system is currently running or was run quite recently"

           

   Article Number:     529665                                   Article Version: 3     Article Type:    Break Fix 
   

 


Product:

 

ViPR Controller,ViPR Controller Controller 3.6 SP2

 

Issue:

 

 

   

      A manual or scheduled discovery of a NetworkSystem is run and the resulting task is marked as "COMPLETE"     
     
      However, the task's message states  :     
     
      "The discovery for this system is currently running or was run quite recently. Resubmit this request at a later time, if needed."     
          
                                                             

 

 

Cause:

 

 

The most recent successful discovery of the Fabric Manager resulted in a pending/incompete task or a ZooKeeper lock that was not released.                                                           

 

 

Resolution:

 

 

   

      A solution exists for this issue, but intervention from Dell EMC technical support personnel is required.     
     
      Support personnel must access your storage system to fix this issue.     
      Contact the EMC Customer Support Center or your service representative for technical assistance and quote this article ID.     
     
      Include the ViPR Controller order history text as well as logs covering the time frame when you contact Dell EMC for technical assistance.     
          

                                                             

 

 

Notes:

 

 

The ViPR Controller controllersvc-discovery log will show the following sequence:   

      vipr1 controllersvc-discovery 2019-01-22 08:58:00,541 [RMI TCP Connection(35117)-xxx.xxx.xxx.xxx]  INFO  DataCollectionJobScheduler.java (line 643) Acquired a lock lock-ns-datacollectionjob- to schedule Jobs       
       
        vipr1 controllersvc-discovery 2019-01-22 08:58:00,547 [RMI TCP Connection(35117)-xxx.xxx.xxx.xxx]  WARN  DataCollectionJobScheduler.java (line 844) NS_Discovery job for <NetworkSystem label> has been running for longer than expected; this could indicate a problem with the storage system
     
     
      vipr1 controllersvc-discovery 2019-01-22 08:58:00,548 [RMI TCP Connection(35117)-xxx.xxx.xxx.xxx]  INFO  DataCollectionJobScheduler.java (line 896) Next Run Time 1547302562778 , Last Run Time 1547298962778     
     
      vipr1 controllersvc-discovery 2019-01-22 08:58:00,549 [RMI TCP Connection(35117)-xxx.xxx.xxx.xxx]  INFO  DataCollectionJobScheduler.java (line 922) NS_Discovery Job for urn:storageos:NetworkSystem:252bade9-e908-494a-95a9-e4dad6739883:vdc1 is in Progress     
     
      vipr2 controllersvc-discovery 2019-01-22 08:58:00,550 [RMI TCP Connection(35117)-xxx.xxx.xxx.xxx]  INFO  DataCollectionJobScheduler.java (line 676) Skipping NS_Discovery Job for urn:storageos:NetworkSystem:252bade9-e908-494a-95a9-e4dad6739883:vdc1     
     
      vipr2 controllersvc-discovery 2019-01-22 08:58:00,574 [RMI TCP Connection(35117)-xxx.xxx.xxx.xxx]  INFO  DataCollectionTaskCompleter.java (line 79) Completed JobType: NS_Discovery, Class: class com.emc.storageos.db.client.model.NetworkSystem Id: urn:storageos:NetworkSystem:252bade9-e908-494a-95a9-e4dad6739883:vdc1, OpId: 1294ddc0-2e59-4498-ba62-861512ead9f0, status: ready, message: The discovery for this system is currently running or was run quite recently. Resubmit this request at a later time, if needed