Did you ever verify that the vCenter plugin is functioning correctly? If it isn't the bug in the KB biting you then it might be an issue with that plugin or its configuration. Also, this is the code from the "Workflow runner" workflow which is where the prep is happening during the stub call out:
System.log("vmUniqueID : " + vCACVm.vmUniqueID);
if (vCACVm.vmUniqueID != null) { // vmUniqueID may be null (i.e at BuildingMachine state)
if (vCACVm.vmUniqueID.indexOf("vcloud") > -1) {
System.log("Got vCloud Director VM ID");
var vdcHosts = System.getModule("com.vmware.library.vcac").getEnabledHosts() ;
for each (var vcdHost in vdcHosts) {
var vCloudVApp = vcdHost.getEntityById(VclFinderType.VAPP, vCACVm.vmUniqueID);
if (vCloudVApp != null) {
break;
}
}
}
else {
System.log("Trying to resolve a vCenter VM");
var sdkConnections = VcPlugin.allSdkConnections;
System.log(sdkConnections.length + " sdk Connections found...");
for each (var sdkConnection in sdkConnections) {
try {
vCenterVm = sdkConnection.searchIndex.findByUuid(null, vCACVm.vmUniqueID, true, false);
} catch(e) {System.log("Error for SDK connection " + sdkConnection.name + " : " + e);}
if (vCenterVm != null) {
System.log("Resolved vCenter VM " + vCenterVm.name);
break;
}
}
}
}
What do you see in your system logs? That should also help shed a little light on things. This code is from the 6.0.1.1 plugin so it may be different in the 6.1 plugin. Anyway take a look at that workflow. You can see it is looping through each of the vCenter connections you have in your plugin. If the connection is not in a responsive state or the plugin is not setup correctly you will not get a hit. Also, if timing wise the VM has not yet been created you won't get a hit. You may need to move what you are trying to do to "machineProvisioned" or at some other point in your workflow look the vm up yourself. Maybe put in an action that loops until the value of vCACVm.vmUniqueID returns something other than null then look the vm up yourself.
