BLUEPRINTS

Written by Simon Eady on 21/9/2015
Published under vRealize Automation
Recently the team I am working with came across an interesting bug/issue with actions missing from deployed VMs. We had checked and double checked the entitlements yet the actions that should be available to the end-user/customer were not listed. Everything appeared to point to a permissions issue until one of the team members noticed something with regards to blueprints in the catalog. Before I continue with what we observed and how we “fixed” it please bear in mind the blueprints were created programmatically.