SamWolf
Enthusiast
Enthusiast

5.5 Code execution failure

Hello,

My team recently upgraded a single orchestrator node to 5.5 and have had a call fail which executes successfully in 5.1.

The code is a simple get of VDC's from an organization as follows:

var vdcs = Orgs[i].getVdcs()

and it produces the following error:

com.vmware.vcloud.api.rest.schema.VdcType (Workflow:Create an Organization VDC / Get Organization vdcs (item2)#6)

Thanks for your input,

Sam

0 Kudos
4 Replies
cdecanini_
VMware Employee
VMware Employee

Have you updated your vCD plug-in to the latest version ?

5.5 -> communities.vmw.../docs/DOC-26474

5.1 -> communities.vmw.../docs/DOC-24919

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos
SamWolf
Enthusiast
Enthusiast

Our vCloud environment has remained at 5.1, will the installation of 5.5 cause conflicts?

0 Kudos
cdecanini_
VMware Employee
VMware Employee

The vCloud Director 5.1 plug-in has been updated to work properly with vCO 5.5. You should use the 5.1 version I linked to check if your issue goes away.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos
SamWolf
Enthusiast
Enthusiast

Hi,

Initially I thought this update had solved the problem but it seems to be persisting. I am currently at version 5.1.576 vCloud director plugin and still running into the "com.vmware.vcloud.api.rest.schema.VdcType" error.

*** An update here, I am having some concerning issues since moving to the .576 version. At first after moving to .576 databases were dropped and after a re-addition the above issue was solved. Today however after working away at things and again running into the Vdctype error once more another reboot has resolved the type issue but again dropped the databases.

This seemingly jumping between to states is very alarming and will definitely to large issues down the road as this is scaled up.

Thanks for your support.

0 Kudos