VMware Aria Automation Extensibility Subscriptions action not getting triggered after upgrade to 8.16.2

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• After upgrading VMware Aria Automation to 8.16.2, the subscription actions that use the condition value as "yes" are not getting triggered during the deployment.
• Deployment is completed successfully, even when the blocking is enabled (Block execution of events in topic).
• The EBS service, which is responsible for Extensibility subscriptions, encountered a null error during the deployment. 
• ebs-app.log

         Service not found at http://<ip-address>:8282/provisioning/config/extensibility-callbacks/<Trace-ID> with status code 404.

• Provisioning service logs located under /services-logs/prelude/provisioning-service-app/file-logs/provisioning-service-app.log contains the following error message

         +++++++++++++++

          WARN provisioning [host='provisioning-service-app-55fdfcb768-8kd4j'  thread='xn-index-queries-3' user='provisioning-yDw1gRiBlZDK1lsS(<User>)' org='<Org-ID>'
     trace='<Trace-ID>'  parent='<ID>'  span=''] c.v.a.s.w.p.x.c.StatefulServiceController.lambda$loadService$20:708 -
     Failed to start service
     /provisioning/config/extensibility-callbacks/<Trace-ID> with 404 status code.

         +++++++++++++++

Environment

VMware Aria Automation 8.16.2

Cause

Identified as a UI issue.

In VMware Aria Automation 8.16.2, when we give the condition value as "yes" in subscription events
the UI sends the yes without the quotes (single/double )to the backend.

For example, if the condition used within a subscription is as below:

event.data.customProperties.addVCNotes == "yes"

In VMware Aria Automation 8.16.2 UI sends the value to backend as addVCNotes: yes

When yes is not single quoted, according to YAML format, it is considered as Boolean. This needs a fix from UI level, so that it sends single quoted yes to backend again.

Resolution

The fix for this issue is included in VMware Aria Automation 8.18.0.

Workaround:

Instead of passing value 'yes', please use 'true' as the condition.

Example:

event.data.customProperties['<property-Name>'] === 'true'