This post is more than 5 years old
4 Posts
0
906
May 12th, 2014 11:00
Vipr Error Provisioning Datastore on vmware
Getting the below error when trying to create a datastore, just set this up and still learning vipr. Was not sure if anyone else had see this. I was able to create a lun on the same storage array, but I can't provision a datstore for vmware using vipr'
| Create Export | Name: CLD-LAB3-VMC-1399918334705, Cluster: CLD-LAB3-VMC, Volume: urn:storageos:Volume:ad2a159c-b96a-479b-9d2f-f867e055f839:, HLU: -1 | a second |
com.emc.vipr.client.exceptions.ViPRHttpException: HTTP ERROR: 500Problem accessing /block/exports. Reason: Could not initialize class com.emc.storageos.exceptions.DeviceControllerException Powered by Jetty:// at com.emc.vipr.client.impl.jersey.ExceptionOnErrorFilter.handle(ExceptionOnErrorFilter.java:44) at com.emc.vipr.client.impl.jersey.ProxyTokenFilter.handle(ProxyTokenFilter.java:23) at com.emc.vipr.client.impl.jersey.AuthTokenFilter.handle(AuthTokenFilter.java:30) at com.sun.jersey.api.client.Client.handle(Client.java:648) at com.sun.jersey.api.client.WebResource.handle(WebResource.java:680) at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:74) at com.sun.jersey.api.client.WebResource$Builder.post(WebResource.java:568) at com.emc.vipr.client.impl.RestClient.post(RestClient.java:133) at com.emc.vipr.client.core.AbstractResources.postTask(AbstractResources.java:332) at com.emc.vipr.client.core.BlockExports.create(BlockExports.java:70) at com.emc.sa.service.vipr.block.tasks.CreateExport.doExecute(CreateExport.java:58) at com.emc.sa.service.vipr.tasks.WaitForTask.executeTask(WaitForTask.java:18) at com.emc.sa.service.vipr.tasks.WaitForTask.executeTask(WaitForTask.java:5) at com.emc.sa.engine.ExecutionUtils.execute(ExecutionUtils.java:63) at com.emc.sa.engine.ExecutionUtils.execute(ExecutionUtils.java:54) at com.emc.sa.service.vipr.ViPRExecutionUtils.execute(ViPRExecutionUtils.java:28) at com.emc.sa.service.vipr.block.BlockStorageUtils.createClusterExport(BlockStorageUtils.java:143) at com.emc.sa.service.vipr.block.CreateBlockVolumeHelper.createAndExportVolumes(CreateBlockVolumeHelper.java:77) at com.emc.sa.service.vmware.block.CreateVolumeAndVmfsDatastoreService.execute(CreateVolumeAndVmfsDatastoreService.java:31) at com.emc.sa.engine.ExecutionEngineImpl.execute(ExecutionEngineImpl.java:191) at com.emc.sa.engine.ExecutionEngineImpl.runService(ExecutionEngineImpl.java:125) at com.emc.sa.engine.ExecutionEngineImpl.executeOrder(ExecutionEngineImpl.java:68) at com.emc.sa.engine.ExecutionEngineDispatcher.processOrder(ExecutionEngineDispatcher.java:43) at com.emc.sa.engine.ExecutionEngineDispatcher$Consumer.consumeItem(ExecutionEngineDispatcher.java:64) at com.emc.sa.engine.ExecutionEngineDispatcher$Consumer.consumeItem(ExecutionEngineDispatcher.java:58) at com.emc.storageos.coordinator.client.service.impl.DistributedQueueConsumer$1.run(DistributedQueueConsumer.java:83) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) |
||
No Events found!
Andrew291
92 Posts
0
May 12th, 2014 13:00
When you run the service in the service catalog it defaults to set the HLU to -1 which is auto. Since you already have luns mapped to the existing storage group you may need to set this higher. Please let me know if this helps.
Andrew
TKSax
4 Posts
0
May 12th, 2014 12:00
Andrew,
Thanks for the reply, I got by that error, I think I had an issue with the virtual pools I had created and associated with the arrays.
I am now getting a different error.
The array is an EMC VNX 5200, with the latest flare.
We already have some luns that were already setup, do I need to scan the array for un-managed volumes first?
Thanks
Andrew291
92 Posts
0
May 12th, 2014 12:00
Can you give us more detail?
Type of array? Other environmental details?
Was this an existing host with masking views already setup?
Can you send the controllersvc.log from /opt/storageos/logs? When you created a lun on the same array did you export it to the same host as device/lun? Was it vmware esxi as well?
Thanks,
Andrew
TKSax
4 Posts
0
May 13th, 2014 13:00
That worked, does that increment from there, or do I need to set that manually? If manually updated, if I import the stuff that was already provisioned in vmware and the vnx will that fix the issue?
Thanks
David
Andrew291
92 Posts
0
May 16th, 2014 09:00
If you set HLU 5 and then run the the service again later I would set HLU 6. If this was a new host ViPR would increment automatically and keep incrementing if you left the default -1. The purpose of the discover and ingest services are for customers who provision their luns at the array level ahead of time and need to import them into ViPR for exporting etc... at a later time. For example you have a raid group that you created 10 luns in....you tell ViPR to discover the volumes from the VNX and it finds these 10 luns. You can then ingest all or some of them to utilize with other ViPR services. Please let me know if you have any other questions.
Andrew