figinhole
Enthusiast
Enthusiast

vRealize Automation (vCAC) and vRealize Orchestrator (vCO) error handeling

One of my vCO workflows are running successfully (I get green check) but vCAC request (that executed the vCO workflow) shows request status failed.

How does vCAC does its error handling from vCO side? Any documentation or example will be great!

QuickQuestion: Does vCloud Automation Center Designer (running on IaaS) takes care of this? Any documentations or tutorials on Designer development?

Thanks,

_Peter

6 Replies
cdecanini_
VMware Employee
VMware Employee

Is this a workflow started from one of IaaS lifecycle stage or is it started from advanced service designer ?

If the request fail it is likely that you have a validation error (i.e a mandatory input not filled) or that the inputs are not set in the same way you do when running the vCO workflow directly.

Also there was a bug in the workflow runner that does the IaaS to vCO integration when getting the VM from the ID. It was running in 5.x and 6.0 but in 6.1 the VM ID changed causing the issue. There is a KB about it.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
figinhole
Enthusiast
Enthusiast

Is this a workflow started from one of IaaS lifecycle stage or is it started from advanced service designer ?

> from IaaS lifecycle.


If the request fail it is likely that you have a validation error (i.e a mandatory input not filled)

> It seems like this is the issue, as request's Status Details on vCAC is "Request succeeded. Created Win-HR-001; with components: ." its suppose to be "Request succeeded. Created Win-001; with components: Win-002, Win-003." - its MultiMachine.


I have custom code in "WFStubMachineProvision" its not doing much just got an if-statement and calling vCO workflow. but some how its messing up the status field/"mandatory input".


Also, using vCAC 6.1


Thanks,

Peter

0 Kudos
figinhole
Enthusiast
Enthusiast

haa.. I did some more digging and apparently if I provision a MultiMachine from vCAC 6.1 and have anything (even just a single "LogMachineEvent" entry - no other code) in custom code of  "WFStubMachineProvision" lifecycle. vCAC shows the Request status as failed! even thought MultiMachine had been provisioned with no issues (and I can also see it under vCAC items).

PS: this is only happening with MultiMachine and not with Single Machine provisioning. Possible Bug VMware ppl?


Thanks

0 Kudos
eocallaghan7319
Contributor
Contributor

I've been having exactly the same issue only mine appears to happening every 3 - 8 deployments. Again only with a MM request with custom code in the WFStubMachineProvisioned lifecycle.

Have you had any further luck with this?

0 Kudos
cdecanini_
VMware Employee
VMware Employee

If I recall well there is a DEM setting for a timeout.

Would the failing ones be the one that last longer ?

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos
McBain
VMware Employee
VMware Employee

Hi All

I'm getting the same issue. With the vRA Request Status reporting as "Failed", then with the Status Details reporting "Request Successed. Created <VNAME>; with components."

This seems to be effecting MMB with with WFStubs that are called by vRO. I have noticed that the request moves to failed as soon as the WFStub starts.

Anyone worked around the issue yet?

0 Kudos