Vipr Controller: When you try to create the first volume for an RP consistency Group, if you to create multiple volumes for a RecoverPoint CG you will get a Null Pointer Exception


   Article Number:     533547                                   Article Version: 2     Article Type:    Break Fix 




ViPR Controller





The user is unable to create multiple volumes in a Vipr Controller catalog service when you are creating volumes for a RecoverPoint Consistency Group. A null pointer exception is given.   

2019-04-22 12:24:45,927 [122|cgCreateStep|1b4453d6-c2bb-4f3d-9735-93e2c482d9d1714d0134-52b4-4fda-a5ad-4de3f2526820] ERROR (line 2180) RecoverPoint cgCreateStep step failed: Exception:com.emc.storageos.recoverpoint.exceptions.RecoverPointException: Failed to create RecoverPoint consistency group ViPR-NEWCG1: java.lang.NullPointerException        at com.emc.storageos.recoverpoint.impl.RecoverPointClient.createCG(        at com.emc.storageos.protectioncontroller.impl.recoverpoint.RPDeviceController.cgCreateStep(        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)        at sun.reflect.NativeMethodAccessorImpl.invoke(        at sun.reflect.DelegatingMethodAccessorImpl.invoke(        at java.lang.reflect.Method.invoke(        at com.emc.storageos.volumecontroller.impl.Dispatcher$        at java.util.concurrent.Executors$        at        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(        at java.util.concurrent.ScheduledThreadPoolExecutor$        at java.util.concurrent.ThreadPoolExecutor.runWorker(        at java.util.concurrent.ThreadPoolExecutor$        at by: java.lang.NullPointerException        at com.emc.storageos.recoverpoint.impl.RecoverPointClient.configureCGSettingsChangeParams(        at com.emc.storageos.recoverpoint.impl.RecoverPointClient.createCG(        ... 13 more    






This is a code bug that Vipr Controller engineering will correct in a future release of Vipr Controller                                                           







      At this time, the problem can be worked around by only creating 1 volume when creating the very first volume.     
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.   







From the ViPR Controller GUI, you may see this error:   
    EE screenshot of error