After recently upgrading from 6.0.1 to 6.1, we are unable to build machines that call the stub workflow WFStubBuildingMachine. This worked properly prior to the upgrade. If we remove this workflow, then machines build okay, but since we have numerous items occurring in vCO (vCenter annotations, AD group created, new machine name assigned, etc.) that are called by that stubworkflow, machines build without it are useless to use.
Here are the 3 stub workflows that we have configured via custom properties. Note: We do not have any values assigned, but never did before the upgrade either. I assume a value is not required as long as you are okay with vCAC picking the latest rev of the workflow when it runs?
After requesting a machine be built that includes calling WFStubBuildingMachine, it eventually times out and the following error is shown in the logs:
We've tried the following already without success:
We are down hard because of this. We'd prefer not to roll back even though we have good backups, as if no one else is experiencing this issue then VMware will likely not get to the root of it and we won't be able to upgrade to 6.1 down the road with confidence.
One thing we are curious about is whether the vCO customization workflow as shown in this post below hasto be run again after upgrading from 6.01 to 6.1? We didn't think so as it's not referenced in any upgrade guides, documentation, or blog posts, but just curious if anyone else did it. We didn't want to do it as it will wipe out what changes have been made to the stubworkflows prior to it. http://www.vmtocloud.com/how-to-extend-vcac-with-vco-part-1-installation/
Has anyone seen this or anything similar? Even if you haven't, do you have any suggestions to try?
In case anyone else runs into this issue, here is what was done to resolve it with the assistance of the vCAC development/support team:
It appears the 6.1 upgrade does not recompile/adjust the stub workflows if they are referencing dll's that are upgraded as part of the 6.1 upgrade process. Our stub workflow was referencing a dll that was replaced with a newer version as part of the 6.1 upgrade. Following the above procedure, recompiled the workflow with the newer dll.
It would be nice if the vCAC upgrade process walked through the stub workflows and did this for you or at least warned you. Hopefully this is something that will be considered for a future version.
In case anyone else runs into this issue, here is what was done to resolve it with the assistance of the vCAC development/support team:
It appears the 6.1 upgrade does not recompile/adjust the stub workflows if they are referencing dll's that are upgraded as part of the 6.1 upgrade process. Our stub workflow was referencing a dll that was replaced with a newer version as part of the 6.1 upgrade. Following the above procedure, recompiled the workflow with the newer dll.
It would be nice if the vCAC upgrade process walked through the stub workflows and did this for you or at least warned you. Hopefully this is something that will be considered for a future version.