Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

2 event broker subscriptions (blocking) running in parallel in vRealize Automation 7.x (57632)

Last Updated: 10/23/2018Categories: TroubleshootingTotal Views: 4573Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Two event broker subscriptions (configured as blocking) that incorrectly runs in parallel resulting in a failure in vRO as one of the properties is NULL.

You see this error similar to:

The following component requests failed: RHEL73. Request failed: appluv0ba0: sendEBSMessage15(workflow=0a411c28-70ce-41f7-b7c4-47edfb67eda5) Error in state VMPSMasterWorkflow32.BuildingMachine phase PRE event (queue = 9c1bc78b-fd31-4c7a-86b2-ab1837f0ae9c): Extensibility consumer error(20999) - TypeError: Cannot read property "cluster" from null (Workflow:Update NW Adapter / Get Properties (item1)#32).

In the /var/log/vmware/vcac/catalina.out file, you see entries similar to:

vcac: [component="cafe:advanced-designer" priority="INFO" thread="workflowStatusCheckExecutor-5" tenant="" context="vOonzt5q" parent="" token="wv6sj95l"] com.vmware.vcac.designer.service.impl.ExecutionStatusChecker.call:118 - Going to cancel expired request 'cf835084-c7c2-43d7-a593-1497221a929d' with o11n-gateway run request 'cfe042a6-195e-4e89-9ec9-b802ee615864' for catalog request id '33075c5f-75e7-426a-b3da-f1964a19cb42' in tenant 'Production'

Checking the entries in asd_workflowrunrequest in the vPostgres database highlights a time difference between createdate and completedate. The completedate entries will show entries based off the createdate, offset by whatever the time zone difference is between the VA that is servicing the request and the VA that is hosting the primary Postgres database.

select id, executionstate, createdate, expirydate, completedate from asd_workflowrunrequest where expirydate is not null and executionstate = 'canceled' order by createdate;

For example:
id                                   | executionstate  |  createdate              | expirydate              | completedate
c49a7ad1-5b3a-4be0-b905-47f04a168305 | canceled        |  2018-07-25 15:23:29.418 | 2018-07-25 15:28:29.397 | 2018-07-25 16:23:30.127
35daa843-53f8-42c6-a7cc-c08cf6f6bcb5 | canceled        | 2018-07-25 15:27:53.432  | 2018-07-25 15:37:53.409 | 2018-07-25 16:28:00.387
84857894-1ea5-4ce5-9cb1-604952b23286 | canceled        | 2018-07-25 15:32:17.446  | 2018-07-25 15:42:17.422 | 2018-07-25 16:32:30.383

In the /etc/sysconfig/clock on all Virtual Appliances in the vRA Cluster, you see different time zone across the nodes similar to:

<<VA1_fqdn>>
TIMEZONE="Europe/London"
DEFAULT_TIMEZONE="US/Eastern"

<<VA2_fqdn>>
TIMEZONE="Europe/London"
DEFAULT_TIMEZONE="US/Eastern"

<<VA3_fqdn>>
TIMEZONE="Etc/UTC"
DEFAULT_TIMEZONE="US/Eastern"

Cause

This issue occurs due to the inconsistency in the time zone configuration across the VAs. This makes the WorkflowExecutionExpiredWorker assume that the workflow has started an hour earlier than expected and cancels the workflow as soon as it finds it.

Note: Configuring a timezone is optional as per the vRealize Automation documentation, However, as per the guidelines for adding other VAs to the cluster, Select Admin > Time Settings, and set the time source to the same one that the rest of the cluster appliances use.

Resolution

This is a known issue affecting VMware vRealize Automation 7.3.x.

Currently, there is no resolution.

Workaround

To work around this issue, follow either one of the workarounds to configure the same timezone across all VAs to match the primary VA.

Workaround 1

Log in through SSH to VA appliance.

Confirm the contents of /etc/sysconfig/clock.

Run the /opt/vmware/share/vami/vami_set_timezone_cmd to update the time zone.

Confirm the contents of /etc/sysconfig/clock.

Reboot the VA appliance and confirm time with 'date' command.

Workaround 2

Update the timezone through the VA VAMI > System > Time Zone.

Reboot the VA appliance and confirm the time with 'date' command.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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