Anyone out there using the vRO plugin from EMC for XtremIO and the "Datastore Expand" workflow? This workflow seems like it should expand a datastore on the VMware side AND in doing so, expand the underlying XtremIO LUN as well prior to expanding the datastore. This consistently will expand my XtremIO LUN, but fail on the datastore expand with an error that the full partition is in use. Running this workflow manually there is never an option to select "Extend" because the datastore is initially not "extendable" as one would expect. So it seems this workflow is not ordered correctly or doesn't do what it claims it can do, but wanted to see if anyone else has used it to confirm or deny those thoughts.
What version of the XtremIO vRO plugin are you using? Hopefully the 1.1 version if not please switch to that version and retry. Having said that the 1.1 version of the workflow will first detect whether or not the datastore can be expanded in place without the need for expanding the XtremIO volume. If the datastore can be expanded without expanding the XtremIO volume you will have the opportunity to do so. If the XtremIO volume must first be expanded you must enter in the new size of the XtremIO volume. When the workflow is run the volume will first be expanded to the new supplied size and then datastore will also be expanded. I believe only the 1.1.0 version of the workflow has this capability, the 1.0.0 version does not. if this does not solve your issue then I suggest you open up a case with customer support in order to get proper resolution for this issue.
Thanks for the quick reply. I am using v 1.1.0 of the plugin. Your synopsis is exactly what I had expected as well but it is not working like that and when it detects that my datastore has no space to be expanded, it will blank out the Expand drop down and just allow me to expand the underlying volume and give it a new size. When I increase the underlying size of the LUN, it does go out and increase the XtremIO LUN as expected, but then bombs out on expanding the datastore with an error of "The datastore is not expandable -- the entire partition maybe in use (Workflow:Datastore Expand/Datastore Expand (item1)"
It's almost as if the ordering is incorrect or it is not refreshing the value or noticing that the datastore now has space to be expanded - as if it is stuck on the first query of the datastore when the workflow was initially run (when it really wasn't possible to expand).
I've tried banging around a couple of items and making a copy of the workflow, but just haven't gotten to far. I'll look at the support case route if you think that is the best route and post any answers back here. Not sure if this is a bug or something on my end.
Glad to read you are using the 1.1.0 workflows. This error is obviously the key to the issue as you have noted:
>>> "The datastore is not expandable -- the entire partition maybe in use (Workflow:Datastore Expand/Datastore Expand (item1)"
Here is something to try. It's possible we need a call to the "host refresh" workflow after the call to the volume expand workflow but prior to expanding the datastore. We can try this out two different ways. The first would be to modify the copy of the "Datastore Expand" workflow and add in a call to the host rescan workflow after the volume is created but before the datastore is expanded.
The other way would be to run the volume expand workflow first which is in the XtremIO Volume Management folder. After you run that then run the Host Rescan workflow for the host or hosts that can see this volume. Then run the Datastore Expand workflow. The Datastore Expand workflow should detect that the volume is larger than the datastore and allow you to expand the datastore in place without first expanding the volume.
Let me know how that goes.
Also what is the initial size of the volume and what is the new size of the volume? How many hosts is the volume being exposed to? Also how many additional volumes are also exposed to the same hosts?
Thanks again for the quick reply. I agree on your thoughts. Let me try to get the first option in place and figure that out in vRO. I like this approach because I'd ideally like to have a single workflow to call that does it all. I am using this to catch an SNMP trigger and automatically expand the LUN and Datastore for a customer so in the larger code that is needed to call this, I think it works cleaner if I am just calling one workflow versus a couple. Let me try to work on this and get back to you asap.
For the volume size, I have tested this a bunch of times trying to fix this error so right now the LUN is 160GB in size. I increment it by 10GB each test. It is presented to an ESX cluster of 6 hosts right now which also see about 8 other LUNs from this same array.
Thanks for the help and I'll get back asap once I can get option #1 in effect to test it.
Sounds good. Also if you manually run the host refresh workflow now, and then run the datastore expand workflow it should give you the opportunity to expand the datastore in place. That would tell us if we are on the right track pretty quickly. I'll wait to hear back from you.
good Idea - I will test that out after a failed expansion run and let you know. I think I figured out an added the Host Rescan workflow so once I get that to save OK, I will run that other test. I suspect you are right since I can re-run the workflow after an initial failure and then I am presented with "Expand" which expands the datastore on the second run just fine - so my gut tells me you are on the right path. thanks!
So after troubleshooting this for a bit, I am starting to think the Host Rescan workflow is not working because I can't run it as standalone with the following error always coming up:
item: 'Host Rescan/item2', state: 'failed', business state: 'null', exception: 'Error when rescanning undefined. Reason: TypeError: Cannot read property "configManager" from null (Workflow:Host Rescan / Host Rescan (item1)#60)'
workflow: 'Host Rescan' (d34ad379-37d6-498f-a11a-f42fb3f74222)
I can do a Host List workflow with no issues and the vCenter List workflow with no issues, but some of the Host workflows are failing (I haven't touched any of these, so not sure if they came like that?". I get errors like above running the Host Rescan and Host Show workflows. I did not add a vCenter with the XtremIO vCenter Add workflow, rather I did it with the built-in vRO vcenter add and these other workflows see it fine. The vCenter Add workflow actually pops up from the start with 2 validation errors. I don't think this is due to anything I did since I never touched these before running them tonight and I can't edit the imported workflows without making so not sure if you see this in your environments by default?
I opened a case, but they weren't sure of where to route it and couldn't help initially so I am waiting on that as well.
It's a little strange that the Host Rescan workflow is failing to run, we simply call into the VMware supplied workflow for this. It looks like the error is coming from the vmware supplied workflow that we call. What version of vRO are you running with?
Hi Rich, I am running the latest 7.3 vRO appliance. I thought I saw it supported 7.x in one of the guides - is 7.3 a potential issue?