VCAP-CMA Deploy – Objective 4.2/4.3

Disclaimer: These are my notes from studying for the 3V0-31.18 exam. If something doesn’t make sense, please feel free to reach out.

The main goal for the whole of section 4 is to know where to start with troubleshooting various aspects of vRealize Automation.

Objective 4.2 – Troubleshoot Tenant Operations

References

• Installing vRealize Automation
• Configuring vRealize Automation
• Objective 2.4 – VCP7-CMA

What kind of issues might you run into with respect to tenant operations?

• Users without access to the correct role
• Approval policies not firing
• Creating new tenants

Following my blog post from the VCP-CMA, I’d want to be very familiar with what access a single role grants. What does an IaaS administrator get different to a tenant administrator etc.

To check on an approval policy, first I’d double check it was linked to the correct item within the entitlement.

Then I’d just sanity check any conditions you’ve attached to the policy. I often see the less than/greater than the wrong way round.

When creating new tenants there are a number of items that will need to be created for it to be useful:

• New directory connector to AD
• New business groups
• New reservations
• Roles will need (re)allocating

Exactly the same as creating them for the first tenant.

Objective 4.3 – Troubleshoot Provisioning Issues

In addition to the references at the top of the post, I want to point out this awesome post over at orchestration.io on troubleshooting provisioning – https://orchestration.io/2017/05/01/troubleshooting-vrealize-automation-provisioning/

Well worth a read if you want in depth detail on where to look for any issues with provisioning.

Before you get to that level of trawling logs, it’s worth checking on the reservations (as mentioned in the previous post):

• Does the reservation have enough free capacity to accommodate the request?
• Does the reservation have access to the capabilities required by the blueprint?

It’s also always worth checking the endpoint is configured correctly and that data collection is occurring.

That covers the IaaS requests, but what if an XaaS request is failing?

• Is vRO running?
• Did the workflow start?
• Is there any logs on the failed workflow?

Check within vRO, under the task to see the instances that have run, check the date. The icon next to the runtime will tell you if it’s been successful or otherwise. If you select the run itself, you can then browse the logs to find out what’s happening during execution.

I’d expect you to need to be able to read enough Javascript to understand what the workflow is doing. Nothing more than a basic understanding.