Hello! I have exactly the same issue (java NullPointerException) on ScaleIO and ViPR on VMware vSphere 6.0! I reinstalled the two solutions without results. Always fail task: CREATE EXPORT GROUP (create export group operation).
I have build the ScaleIO 1.31. Can create the volume for a host. But it can not create the volume and datastore for a cluster in Vcenter. It failed during creating the volume. Here is the log message:
Date
Level
Message
Aug 4th 2015, 9:22:34 am
INFO
Logged into vCenter 'Storage_Vcenter' VMware vCenter Server 5.5.0 build-2442329
Aug 4th 2015, 9:22:34 am
INFO
Host '10.204.28.169' connection state: connected
Aug 4th 2015, 9:22:34 am
INFO
Host '10.204.28.170' connection state: connected
Aug 4th 2015, 9:22:35 am
INFO
Host '10.204.28.171' connection state: connected
Aug 4th 2015, 9:22:35 am
INFO
Targeting Cluster 'ScaleIO' containing 3 hosts
Aug 4th 2015, 9:22:35 am
INFO
Host '10.204.28.170' connection state: connected
Aug 4th 2015, 9:22:56 am
ERROR
Error 60002: Error encountered while trying to create volume. Could not create volume ScaleIO volume: Error: Unknown parameters in command line; Rollback error: Volume does not exist or is already deleted
com.emc.vipr.client.exceptions.ServiceErrorException: Error 60002: Error encountered while trying to create volume. Could not create volume ScaleIO volume: Error: Unknown parameters in command line; Rollback error: Volume does not exist or is already deleted at com.emc.vipr.client.core.impl.TaskUtil.checkForErrors(TaskUtil.java:91) at com.emc.vipr.client.Tasks.waitFor(Tasks.java:131) at com.emc.sa.service.vipr.tasks.LongRunningTasks.executeTask(LongRunningTasks.java:47) at com.emc.sa.service.vipr.tasks.LongRunningTasks.executeTask(LongRunningTasks.java:11) at com.emc.sa.engine.ExecutionUtils.execute(ExecutionUtils.java:80) at com.emc.sa.engine.ExecutionUtils.execute(ExecutionUtils.java:71) at com.emc.sa.service.vipr.ViPRExecutionUtils.execute(ViPRExecutionUtils.java:41) at com.emc.sa.service.vipr.block.BlockStorageUtils.createVolumes(BlockStorageUtils.java:201) at com.emc.sa.service.vipr.block.CreateBlockVolumeHelper.createAndExportVolumes(CreateBlockVolumeHelper.java:71) at com.emc.sa.service.vmware.block.CreateVolumeAndVmfsDatastoreService.execute(CreateVolumeAndVmfsDatastoreService.java:98) at com.emc.sa.engine.ExecutionEngineImpl.execute(ExecutionEngineImpl.java:201) at com.emc.sa.engine.ExecutionEngineImpl.runService(ExecutionEngineImpl.java:131) at com.emc.sa.engine.ExecutionEngineImpl.executeOrder(ExecutionEngineImpl.java:72) at com.emc.sa.engine.ExecutionEngineDispatcher.processOrder(ExecutionEngineDispatcher.java:50) at com.emc.sa.engine.ExecutionEngineDispatcher$Consumer.consumeItem(ExecutionEngineDispatcher.java:94) at com.emc.sa.engine.ExecutionEngineDispatcher$Consumer.consumeItem(ExecutionEngineDispatcher.java:88) at com.emc.storageos.coordinator.client.service.impl.DistributedQueueConsumer$1.run(DistributedQueueConsumer.java:87) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)
Doesn't look like a lot of information in this log. Have you tried with other vcenter clusters or hosts? So basically you can export a volume to a vcenter cluster but just not a datastore? Have you tried another datastore name? Please provide as much detail as possible. Providing full logs from the ViPR GUI would help us as well. Is this a greenfield vcenter or does it have existing exports to these hosts/cluster?
I am so sorry ,I have updated the log. The log file should be controllersvc.log, not be log2.txt. And I already know where was wrong. I just add a "space" when i define a volume name.Then give out this error. Thank you so much .
Y1Udba1GsO12085
71 Posts
0
July 31st, 2015 00:00
Hi,
As per the latest ViPR support matrix, only ScaleIO 1.30 and 1.31 are supported with ViPR 2.2 and 2.3.
Regards
Grypa
8 Posts
0
July 30th, 2015 05:00
Hello! I have exactly the same issue (java NullPointerException) on ScaleIO and ViPR on VMware vSphere 6.0! I reinstalled the two solutions without results. Always fail task: CREATE EXPORT GROUP (create export group operation).
Andrew291
92 Posts
0
July 30th, 2015 15:00
Which version of scaleio are you using? 1.30 or 1.31? ViPR 2.2 or 2.3?
littleboy1
1 Rookie
•
53 Posts
0
July 30th, 2015 18:00
ScaleIO version is 1.32 and VIPR version is 2.3.The ScaleIO is deployed by VMware plugin in Vcenter 6.0.
littleboy1
1 Rookie
•
53 Posts
0
July 30th, 2015 18:00
yeah,during the CREATE EXPORT GROUP task. I can't find out why. The NullPointerException, how could this coming out?
Grypa
8 Posts
0
July 30th, 2015 22:00
I get this error on ScaleIO 1.32 and ViPR 2.2 and 2.3...
littleboy1
1 Rookie
•
53 Posts
0
July 31st, 2015 01:00
Oh,I am sorry. I didn't read the document about the ViPR support matrix.Do you know when the VIPR will support the ScaleIO 1.32?
littleboy1
1 Rookie
•
53 Posts
0
July 31st, 2015 01:00
ViPR Support Matrix - REV 14c.pdf
We should read this document firstly.
littleboy1
1 Rookie
•
53 Posts
0
August 3rd, 2015 23:00
I have build the ScaleIO 1.31. Can create the volume for a host. But it can not create the volume and datastore for a cluster in Vcenter. It failed during creating the volume. Here is the log message:
And I want to know where can i find the detail log?
thank you
Andrew291
92 Posts
0
August 4th, 2015 05:00
check out the controllersvc.log
/opt/storageos/logs....
littleboy1
1 Rookie
•
53 Posts
0
August 4th, 2015 20:00
here is the log info.But i can not find the error from here, Could you help me ?
1 Attachment
controllersvc.log
Andrew291
92 Posts
0
August 6th, 2015 07:00
Doesn't look like a lot of information in this log. Have you tried with other vcenter clusters or hosts? So basically you can export a volume to a vcenter cluster but just not a datastore? Have you tried another datastore name? Please provide as much detail as possible. Providing full logs from the ViPR GUI would help us as well. Is this a greenfield vcenter or does it have existing exports to these hosts/cluster?
littleboy1
1 Rookie
•
53 Posts
0
August 6th, 2015 18:00
I am so sorry ,I have updated the log. The log file should be controllersvc.log, not be log2.txt. And I already know where was wrong. I just add a "space" when i define a volume name.Then give out this error. Thank you so much .