vCO vCloud plug-in TypeError: Cannot find function

[teckmeng]

Hi, I just installed vCloud v1.5 plug-in for vCO and I can browse the vCloud's inventory successfully in vCO. However, when I attempt to start any vCloud workflow, it will fail with an error that the function cannot be found. For example, when I run the workflow "Power on a vApp", it will fail with error "TypeError: Cannot find function poweron". The vCloud packages seem to be installed properly but the workflows are not linked to them.

I am using the vCO appliance and I am not sure if this is a bug. From what I read from the Internet, vCloud plug-in installation should be very straight-forward and I don't understand what's wrong with my installation. Any advice?

[cdecanini_]

A cannot find function error on vCloud Director plug-in means the plug-in cannot resolve an url to an object. You end up with an object of type "notFound" which does not have the methods you are expecting on the original object.

Most of the time this is because of a mismatch of the url set up in the vCloud Director plug-in and the API URL set in vCloud Director. Often this happens in load balanced Cells configurations.

Christophe.

[teckmeng]

I suspect the vCloud Director was probably not setup properly as the SSL certificate common name is "mycloud.localdom" while its hostname is "vcloud.corp.vcd.local". I have added both entries into vCO's local host file and hence can ping to it via either name from vCO console. Also, there is only one cloud cell and hence there shouldn't be any API URL issues, right?

I imported both SSL certificates (mycloud.localdom and vcloud.corp.vcd.local) into vCO configuration and still it doesn't work. For some reasons, I also cannot set the vCloud Director hostname (I tried both listed above) in the vCO vCloud Plugin configuration. It gives the error "Malformed URL. Host: vcloud.corp.vcd.local, Port: 443"

Any advice on what else should I check?

[cdecanini_ · Accepted solution]

If I remember well using invalid domain names is not accepted. This is certainly why you get the malformed URL.

Christophe.

[teckmeng]

The problem is resolved after I fixed the SSL certificate on the vCloud Director with a proper DNS hostname. Thanks for all the help!