ViPR Controller: "Error 2000: Unable to find entity specified" when running a custom catalog entry

           

   Article Number:     525313                                   Article Version: 4     Article Type:    Break Fix 
   

 


Product:

 

ViPR Controller

 

Issue:

 

 

The user is trying to run a custom ViPR Controller Catalog entry that was created/modified and it errors with the following message:   
        

      Error 2000: Unable to find entity specified in URL with the given id urn:storageos:VirtualPool:xxx-xxx-xx-xxx:vdc1   
   

      The same type of error could occur for other URNs and not just limited to Virtual Pools.   

                                                             

 

 

Cause:

 

 

Previously the user had used ViPR Controller's functionality to copy an existing catalog entry, rename the copy, and edited the new catalog entry to "Lock in" some values for some of the catalog entries options.   
   
    The custom catalog entry was linked to a specific virtual Pool that had since been deleted from VIPR-C.
                                                           

 

 

Change:

 

 

In this scenario, the user had deleted a virtual pool from their ViPR Controller setup.    
     
                                                           

 

 

Resolution:

 

 

   

      Workaround:     
     
      Since the Virtual Pool (and Virtual Array in this example) were deleted via the GUI, and since the user had previously locked in those values in a Catalog entry, the workaround was to re-edit the catalog entry and select new values (instead of the old deleted values).     
     
      When the user edited the problem catalog entry, they noticed that the "Locked" check box was still selected but the "value" field was empty:     
     
      screenshot of catalog editing screen     
     
      The user should either select a new value or uncheck the box if they do not want to lock in a specific value.     
     
     
      Resolution:     
     
      ViPR Engineering is currently addressing this problem, but has not provided a fix in a released patch.     
      This solution will be updated with the patch when it has been released.