VMware Cloud Community
Dino_D
Contributor
Contributor
Jump to solution

"All machines EBS-provisionedState V0001" WorkFlow failing after upgrade from vRA 7.0 to 7.2

We have custom workflow "All machines EBS-provisionedState V0001" which was working fine but after we upgraded form vRA 7.0 to 7.2 it stopped working.  The provisioning goes through builds the vm and in the end it deletes the deployed vm from the vCenter:

[2018-09-14 14:33:47.976] [E] Error in (Workflow:AddtoSCCMTaskSequences / Scriptable task (item1)#2) TypeError: Cannot read property "guestOperationsManager" from undefined

[2018-09-14 14:33:48.058] [E] (com.vmware.pso.GuestOps/testVmToolsForGuestOps) Error in (Dynamic Script Module name : testVmToolsForGuestOps#0) TypeError: Cannot read property "guestOperationsReady" from undefined

[2018-09-14 14:33:48.108] [E] Workflow execution stack:

item: 'All machines EBS-provisionedState V0001/item17', state: 'failed', business state: 'Test VM tools', exception: 'Exception binding empty'

workflow: 'All machines EBS-provisionedState V0001' (07aab4e2-b47f-497a-89a0-e008a430ab34)

0 Kudos
1 Solution

Accepted Solutions
iiliev
VMware Employee
VMware Employee
Jump to solution

Judging by the action module name, it has been developed by PSO guys, so it will be better to contact them.

View solution in original post

0 Kudos
5 Replies
iiliev
VMware Employee
VMware Employee
Jump to solution

Well, what the errors say is that there are uninitialized variables on the first line in scripting action 'com.vmware.pso.GuestOps/testVmToolsForGuestOps' and on the third line in item1 in workflow AddtoSCCMTaskSequences.

Without having access to this action/workflow, and context in which they are called, it is impossible to say what exactly is the problem.

0 Kudos
Dino_D
Contributor
Contributor
Jump to solution

Thank you for getting back to me on this issue.  Is there a way to export that part of the workflow and send I to you?

0 Kudos
iiliev
VMware Employee
VMware Employee
Jump to solution

No, workflows can only be exported as a whole. Or a scripting code can be copy/pasted.

The problem is that these types of errors could depend on environment/runtime context, so it is best to troubleshoot them in the environment where the problem can be reproduced consistently.

0 Kudos
iiliev
VMware Employee
VMware Employee
Jump to solution

Judging by the action module name, it has been developed by PSO guys, so it will be better to contact them.

0 Kudos
Dino_D
Contributor
Contributor
Jump to solution

Thank you

0 Kudos