VMware Cloud Community
alcaron2k2
Contributor
Contributor

[VRA8.1] Could not start delete workflow for type Custom.Blah due to Could not find vRealize Orchestrator Integration with id null!

I have been pulling my hair out only to find out that the issue isn't woth my workflows, it is with ANY custom resource Destroy lifecycle action.

The Create lifecycle action runs just find, the Destroy always gives this error. ALWAYS.

I am using the embedded vRO instance if that matters.

Reply
0 Kudos
2 Replies
legioon
Enthusiast
Enthusiast

This is not orchestrator specific error. When you create Custom Resource, you need the set correct "External Type" value as you can see at below. For Example ; You want to create vCenter Folder with Custom Resource. Object name and output parameter is  "VC:VmFolder" and stores all information about this folder such as Id, location, parent folder etc... When you create folder with blueprint, vRO workflow works and stores all information about this folder in "VC:VmFolder" object by output parameter. Then, when you delete your deployment, this folder will be removed because of custom resource will pass folder informations to "Delete Virtual MAchine Folder" workflow. I hope I could tell.

pastedImage_0.png

pastedImage_1.png

pastedImage_6.png

Reply
0 Kudos
alcaron2k2
Contributor
Contributor

This leads to something I have searched high and low for an answer to and never found an explanation.

"Custom resource with the same external type already exists. Use a different external type."

So lets say my output type is a string right, I create a custom resource for a workflow that outputs a string, and now I go create another workflow that also spits out a string...and then I go to create a custom resource that...oh wait no you can't because you can only create ONE custom resource for each external type without getting that error.

Which seems...insane...

Reply
0 Kudos