Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Identifying the root cause of vRealize Automation 7.x provisioning failures (79611)

Last Updated: 6/29/2020Categories: TroubleshootingTotal Views: 5048Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article focuses on helping you identify the root cause or point of failure for provisioning tasks in vRealize Automation 7.x.  The focus is on later releases of 7.x but should be valid for most 7.x versions.

Resolution

Troubleshooting Methodology and Best Practices

Review the error messages starting with the error listed in the deployment failure itself.

Next you can review additional logs under Administration, Monitoring, Log for more information.

If root cause is still elusive, try to reduce complexity of your blueprint to a simple provision of an object to an endpoint.  This will help you identify if the problem is within the blueprint or if it's at the endpoint or endpoint configuration.

If the issue appears to be occurring within the Event Broker component, review the logs under Administration, Events, Event Logs.

When possible, try the same provisioning outside of vRA (directly on the endpoint) to narrow down the source layer of the failure.

Review endpoint configuration in Infrastructure and connectivity using the 'Test Connection' option.  Check that data collection is completing properly.

Log Analysis

vRA logs span multiple servers and services. As such, it is easier to perform deeper dive log reviews if you are using a log aggregator like vRealize Log Insight or exporting a log bundle and performing a search throughout the captured files for the errors.

Full logs for vRealize Automation 7

https://kb.vmware.com/s/article/2141175

Logs most important for provisioning analysis

vRA Server Logs (appliances):  /storage/log/vmware/vcac/catalina.out

IaaS Manager Server Logs (Windows):  C:\Program Files (x86)\VMware\vCAC\Server\Logs

IaaS Repository Logs (Windows):  C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Web\Logs\Repository

Finding all events related to a provisioning request

First you will want to collect the context ID for the request by searching for the following text strings in the IaaS Repository logs for the time the machine was first requested: MachineRequest.  In this log event you'll find a 'context=' string.

Perform a new search across all vRA logs for the context id from above.  This will give you a complete list of all events related to the machine request.  You should be able to review these for the exception or failure causing the provision to fail.

Log Analysis Tips

For reviewing logs using the command line the following two methods can help:

Linux: grep –color=always -RHni “contextID” ./* | less -R

PowerShell / Windows: $ContextID = gc <filename.log> | select-string “contextID”

Interop Log Analysis

Event Broker/ vRO failures

If your provisioning is failing due to extensibility/ vRO workflow failures, you can log into vRO (using the account configured in vRA) and review the failed workflows for logic or other possible causes.  This is the easiest method for identifying the failures.

The embedded vRO instances retain the context ID from vRA so when reviewing the logs you can use the context ID to then collect the related workflow ID's.  These workflow ID's can be searched to show all events related to the failing workflow.

NSX Provisioning Failures

If your failure is related to provisioning of NSX components, you can find the full name of the NSX resource that is being attempted from the vRA logs using the string: 'CompID: [NSX'

Using the full name of the NSX resource from above, search the NSX Manager logs for more details related to the objects being created.

AWS Provisioning Failures

Provisioning of AWS operates the same as standard vSphere Provisioning so the above methods and best practices still apply.

When reviewing logs, be aware that the IaaS DEM services are brokering communication to your AWS resources so you will likely find the root cause there.

Azure Provisioning Failures

Provisioning of Azure resources function from vRO and not from vRA Infrastructure services.  For identifying the root cause, it helps to log into the vRO instance (using the account configured in vRA) and review the worklfows runs.  Note there are two places where workflows are stored:

Library\vRealize Automation\Endpoint\Azure - This is where all of the workflows are located for vRealize Automation's native Azure functionality. Used for vRA Endpoints.

Library\Azure\ - This is where all XaaS workflows are located. These are used when you add a vRO Endpoint for Azure and use custom XaaS blueprints and resources.

Other Resources

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
[自動更新のロールアウトの中断]：Workspace ONE Intelligent Hub 20.05 for iOS (Swift) リリースのお知らせ (79488)

KB
•
在 vRealize Automation 8.x 中，容器状态为 "挂起" 或 "已退出" (78929)

KB
•
Workspace ONE UEM インストーラのインストール向け Windows Server 2008 R2 および Windows Server 2012 (R2 以外) のサポート終了 (79538)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 7.x

Take Our Survey

Support Assistant