Troubleshoot failed vRA deployments

Troubleshoot failed vRA deployments

Are you developing the next coolest vRA blueprint ever? Does it maybe involve NSX components? How about software blueprints? As with many efforts that don't quite succeed the first try, so to do issues occur within software during the development process. What happens in vRealize Automation when you try but fail? If you're reading this, you probably know:  it deletes the entire deployment. Not always helpful, especially when writing software components. Fortunately, there's an easy way to fix that. In your blueprint, add the custom property to your deployment called "_debug_deployment" and set the value to "true".

pastedImage_0.png

Now when you request that same item, instead of saying "Failed" and vRA blowing the whole thing up before you've had a chance to figure out what went wrong, the deployment will hang around out there. It'll say "Partially Successful" in your requests so you can distinguish between something that would have failed and when you finally see those successful ones.

pastedImage_1.png

Remove the property once you've got everything working properly. This will preserve some of your hair (if you still have any at all) and make the development process a little easier on you.

Version history
Revision #:
1 of 1
Last update:
‎08-19-2017 04:50 PM
Updated by: