I am having a big problem with the new vcenter plugin on Windows 4.2.1b555.
Say we have a property on an object which is a few properties deep, ie. host.runtime.name (I just made this up as an example), then the first time the workflow runs then it will fail saying it cannot find the property "runtime". If you run it again then it will find the runtime property but fail on the "name" property. If you run it a third time then it will be ok, until you reach the next object property you reference.
Needless to say, this is a game breaker and has effectively broken our environment.
Restarted vco configuration, vco orchestrator service, restarted the server entirely..
Another issue is that when I browse for input from a vCenter (vmfolder or vnetwork) then it will have the "loading" icon then show nothing, I must attempt a number of times (the same time it used to take in the old plugin to return the data) before the data is displayed.
I have downgraded to the 5.0.0 plug-in and the problems have gone away.
Also, I did not experience the "temporary loss" of configuration item data which I was experiencing under 5.0.1 (although I only restarted vco once, so it is too early to tell but under 5.0.1 it was occurring on every restart).
Not to throw a wet blanket on the party but it may be wise for people to apply the update in a test environment before prod.
A few details first:
The vCenter plugin 5.0.0 uses only vCenter property collector to get changes to the properties of the object.
The vCenter plugin 5.0.1 uses the vCenter inventory service and fall back to property collector if not available (but much slower in this way).
This plugin (5.0.1) in some cases had issue with losing attributes/configuration values.
The updated release of vCenter plugin 188.8.131.52 fixes those issues as well as a few others.
Now, based on your description that works with vCenter plugin 5.0.0 and doesn't work with 184.108.40.206, I would suggest that you don't have the vCenter inventory service started or there is some issue with it. So, if you still won't to find out what the issue is with the new version, I would advise to take a look at the vCenter inventory service configuration.
That clears up a few things for me.
We are not running vCenter 5.0 yet (still on 4.1), so no inventory service is available (though an upgrade is planned later in the year).
The 5.0.0 plugin always worked fine, as did the 5.0.1 before this update (although we did experience the loss of attributes) so I guess backward compatability with vcenter 4.1 is not guaranteed?
An interesting thing I found today..
I downgraded to the vCenter 5.0.0 plugin because the 5.0.1-232 broke with our vCenter 4.1 servers (and 5.0.1-192 is not available for download anywhere I can find).
We have a vCenter 5.0.0 server which I tried adding today, with this server enabled the 5.0.0-149 plugin broke as did the 5.0.1-232 when I tested it.
I managed to find a copy of the 5.0.1-192 dar and using this works.
I am not sure if this is a known issue, but using a mix of vCenter 5 and 4.1 servers does not seem to work with the new plugin.
In our case, this will be a problem when we progressively replace our vCenter 4.1 hosts with vCenter 5 as there is no official place to download the 5.0.1-192 plugin, and merely replacing the dar will give a message on the plugin configuration of "Installation corrupted (bad plug-in version)".
The downgrade of the plugin version is not supported by the configurator, so the replacement of the dar file is the way to do it.
The issue preventing the plugin from using 4.x vCenters is fixed. After tests process finish I will provide link for download. It will have bigger build number so you can use the configurator to do the upgrade.
I have uploaded a new version of the vCenter plugin that should fix the issue that you reported with vCenter 4.1 version.
The plugin version 220.127.116.11-244 and could be downloaded from here: http://communities.vmware.com/docs/DOC-19851
Please, let us know if everything is fine with this version for your case when you have a chance.
Note: This is a prereleased version (althought tested and verified) so you could try it out in a test environment first.
Hi Dave,Thanks a lot for your positive feedback!>Thanks a lot for the update, you're a legend!The legend and all the credits go to the engineer who worked on this plugin update Daniel Vatov !Thanks,Igor.