Technical preview version of - VMware vCenter Orchestrator Multi-Node Plug-in 5.1.0

[#1]

Technical preview version of VMware vCenter Orchestrator Multi-Node Plug-in 5.1.0.

Version 5.1.0-66 :

• Fixed compatibility with vCO 5.1.1. Multi-Node plugin refuses to launch remote workflows with error message: "Failed to start remote workflow execution"

Version 5.1.0-68 :

• Fixed - Deploy Package from a Local server results in rights of worklows being changed
• "Add host" - Proxy workflows for the remote server generated based on provided parameter value.

Version 5.1.0-72 :

• Fixed issue with plugin upgrade.
  

Please note, that the attached plug-in is QE verified, but still not a final version.

[Byrdog55]

Thanks for the updates.  I am having a problem calling a simple remote workflow via a proxy workflow.  The remote workflow executes properly ( Creates a computer account in a specific OU) but the proxy returns as failed with:

Unable to convert object, '{remoteToken=com.vmware.o11n.plugin.vcoconn.model.RemoteWorkflowToken@e7e2880d, trigger=ch.dunes.vso.sdk.api.PluginTrigger@7c0458a8}' plugin unexcepted exception : Bad type syntax 'Properties'

[Byrdog55]

Additional information.  My remote workflow inputs are only strings.  I use these strings to locate the Objects needed to create the computer account.

[pslavova]

Hi,

Can you provide a little mmore information about your remote workflow and the vco versions you are using. What are the output object types of the remote workflows?

What versions are the two VCO servers - the remote one and the one with the installed plugin? Also if you can provide the server.log file and the remote workflow, it will be very helpful...

[Byrdog55]

Hi pslavova,

My workflow (local and remote) has no Output parameters, just three input parameters which are all strings.  I just need it to create the account and return that it was successful.

I redeployed two new vCO appliances, both are version 5.1.1 Build Number 2942.  The local and remote work flows execute properly when run manually, I only get the failure when running the proxy workflow, even though the remote flow executes and creates the computer account as expected.   I'll be happy to attach the packages that contain the working workflow, proxy workflow and remote workflow and log file. (I'm looking for how to attach these to this thread).  Feel free to send me an email and I will provide the zip file containing everything.

[Byrdog55]

I was able to determine that I was causing my own issue. It appears that I was over complicating calling the remote workflow that is automatically generated when adding a slave vCO server, by editing the example remote workflow.