Multi node plugin (5.1) and Orchestrator 5.5 appliance

[HolzapfelJ]

Did somebody try the Orchestrator 5.5 Appliance with the Multi Node Plugin (5.1) already?

I'm getting the following error trying to deploy a package to slave hosts (see attachment: error.txt).

Is it because of API differences between 5.1 and 5.5? Do I have to wait for a 5.5 Multi Node Plugin or is it anything I can fix by myself?

[mcfadyenj]

although I haven't looked into the multi node too much, it does appear it is using rest to move content around. I gathered this from the URL that it has in your error log. this is the same url the rest plugin uses.

do you have the rest plugin installed? i could be way off track here as i dont use the multinode, but i do use rest quite heavily.

[HolzapfelJ]

There is nothing mentioned regarding REST plugin in the docs of the multi node plugin, but I tried installing REST plugin on all nodes. It changed nothing I'm getting the same log:

[2014-01-03 12:45:05.342] [I] ==== Deploying [org.xxx] ====
[2014-01-03 12:45:16.275] [I] ==== vco-xxx ==== FAILED
[2014-01-03 12:45:16.282] [E] Unable to import package org.xxx on vco-xxx
[2014-01-03 12:45:16.283] [E] Could not unmarshal to [class com.vmware.o11n.sdk.rest.client.stubs.PackageContentDetails]: unexpected element (uri:"http://www.vmware.com/vco", local:"packages"). Expected elements are <{http://www.vmware.com/vco}package-details>; nested exception is javax.xml.bind.UnmarshalException: unexpected element (uri:"http://www.vmware.com/vco", local:"packages"). Expected elements are <{http://www.vmware.com/vco}package-details>
[2014-01-03 12:45:16.284] [I] ==== vco-xyy ==== FAILED
[2014-01-03 12:45:16.285] [E] Unable to import package org.xxx on vco-xyy
[2014-01-03 12:45:16.285] [E] Could not unmarshal to [class com.vmware.o11n.sdk.rest.client.stubs.PackageContentDetails]: unexpected element (uri:"http://www.vmware.com/vco", local:"packages"). Expected elements are <{http://www.vmware.com/vco}package-details>; nested exception is javax.xml.bind.UnmarshalException: unexpected element (uri:"http://www.vmware.com/vco", local:"packages"). Expected elements are <{http://www.vmware.com/vco}package-details>
[2014-01-03 12:45:16.409] [I] ==== Deploying [org.xyz] ====
[2014-01-03 12:45:18.622] [I] ==== vco-xxx ==== FAILED
[2014-01-03 12:45:18.623] [E] Unable to import package org.xyz on vco-xxx
[2014-01-03 12:45:18.623] [E] Could not unmarshal to [class com.vmware.o11n.sdk.rest.client.stubs.PackageContentDetails]: unexpected element (uri:"http://www.vmware.com/vco", local:"packages"). Expected elements are <{http://www.vmware.com/vco}package-details>; nested exception is javax.xml.bind.UnmarshalException: unexpected element (uri:"http://www.vmware.com/vco", local:"packages"). Expected elements are <{http://www.vmware.com/vco}package-details>
[2014-01-03 12:45:18.624] [I] ==== vco-xyy ==== FAILED
[2014-01-03 12:45:18.624] [E] Unable to import package org.xyz on vco-xyy
[2014-01-03 12:45:18.625] [E] Could not unmarshal to [class com.vmware.o11n.sdk.rest.client.stubs.PackageContentDetails]: unexpected element (uri:"http://www.vmware.com/vco", local:"packages"). Expected elements are <{http://www.vmware.com/vco}package-details>; nested exception is javax.xml.bind.UnmarshalException: unexpected element (uri:"http://www.vmware.com/vco", local:"packages"). Expected elements are <{http://www.vmware.com/vco}package-details>

This entry in the log makes me think: unexpected element (uri:"http://www.vmware.com/vco", local:"packages"). Expected elements are <{http://www.vmware.com/vco}package-details

Seems that maybe something was changed from 5.1 to 5.5 what may need a change in multi node plugin also to make it work with 5.5.

[iiliev]

Multi node plug-in does not depend on REST plug-in and does not require it to be installed.

What was changed in 5.5 - vCO server REST API endpoint URL is now https://[vco-ip]:8281/vco/api/ (in 5.1 it was https://[vco-ip]:8281/api/).

[igaydajiev]

Try using following version of Multi Node plugin : https://communities.vmware.com/docs/DOC-24862

[HolzapfelJ]

Thanks, but I get the same errors than before with your suggested version of the plugin.