We have installed vCO and configured with vCenter and vCloud Director successfully.
But we are not able to execute even sample workflows of Poswering on Vm and all.
1st 2 images are the screen shot of failed workflow in vCenter while rest 2 are of failed workflow vCloud Director.
Please help.
Hi,
Could you provide the version number of the products that you are using? The vCenter and vCenter plug-in for vCO, and the vCloud Director and vCloud Director plug-in for vCO.
Also, from your screenshots, could you provide a shot of the tabs "Variables" and "Logs"?
And how do you run those workflows? Do you start the workflow and then you choose the VM you want? Probably you can do that without problems, can't you? And the inventory for those vCO plug-ins inside the vCO client works fine, doesn't it?
Regards,
Sergio
Hi Sergio,
Thank you for quick response.
Versions: vCenter--4.1 and vCenter plug-in for vCO, 1.0 and the vCloud Director 1.0 and vCloud Director plug-in for vCO. 1.2
Workflow Token Tab is empty; Events tab shows only 2 events 1) created & 2) saved
No Log tab is available 😞
Yes, we started the workflow and then selected VM but its not working; we selected the VM from inventory and then right click on it and selected workflow and then executed it but no luck.
Inventory for those vCO plug-ins inside the vCO client works fine.
Hi again,
Sorry, I meant the tabs "Variables" and "Logs" that appear down on your first screenshot. See my screenshot.
It's very strange that both plug-ins fail like that, running one of their simplest operations. Have you checked that the user which is configured for both plug-ins (it could be the same or not) has the rights to perform the operation of powering on a VM? Or in another way, if you log in the vCenter client or the vCloud Director web client with the user that you have configured... can you power on from there the same VM that you are trying to power on from vCO? Since the inventories of both plug-ins are working fine, I'd check in first instance for some kind of permissions misconfiguration for "update" operations.
Regards,
Sergio
Does other workflows run successfully ?
If all fails it is likely that vCO has issues writing to its database.
Christophe.
Checking for error messages on the server.log file would certainly gives the reasons it is failing
Hi Christophe,
No other workflows are working 😞
Hi,
I found this:
2011-09-30 17:24:18.149+0530 INFO [Execution] Executing workflow 'Power On VM'
2011-09-30 17:24:18.274+0530 WARN [WorkflowHandler] Error in execution of workflow 'Power On VM'
java.lang.NoClassDefFoundError: Could not initialize class com.vmware.vmo.plugin.vix.VixServer
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at ch.dunes.vso.sdk.SDKModuleDescription.defineInScope(SDKModuleDescription.java:453)
at ch.dunes.vso.sdk.ModulesFactory.defineInScope(ModulesFactory.java:409)
at ch.dunes.scripting.jsmodel.Definitions.doDefineModelInScope(Definitions.java:94)
at ch.dunes.scripting.jsmodel.Definitions.defineModelInScope(Definitions.java:48)
at ch.dunes.scripting.server.script.MainScriptingObject.<init>(MainScriptingObject.java:144)
at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.execute(WorkflowHandler.java:183)
at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.run(WorkflowHandler.java:155)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
2011-09-30 17:24:18.289+0530 WARN [WorkflowHandler] Unable to Clean Scripting context
java.lang.NullPointerException
at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.end(WorkflowHandler.java:527)
at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.execute(WorkflowHandler.java:257)
at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.run(WorkflowHandler.java:155)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Disable the VIX plug-in in the web configuration and try again.
Was the VIX plug-in ever used successfully ?
Yes, as Christophe points out, most probably the error comes from the VIX plug-in...
Some more info:
- http://communities.vmware.com/message/1637297#1637297
- http://communities.vmware.com/message/1735589#1735589
- http://communities.vmware.com/message/1744403#1744403
Regards,
Sergio
Thank you very much Sergio & Christophe.
It worked.
Thanks ton....