LCMBLACKSTONE213012 Error while capturing and releasing content containing special characters in Aria Suite Lifecycle

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• A LCMBLACKSTONE213012 error is seen in the Aria Suite Lifecycle UI when capturing and releasing content containing special characters in Aria Suite Lifecycle.

Error Code: LCMBLACKSTONE213012
LCMBLACKSTONE213012
Received exception while triggering pipeline action on blackstone.

• The /var/log/vrlcm/vmware_vrlcm.log logfile contains a stack trace similar to:

com.vmware.vrealize.lcm.common.exception.LcmException: Request execution failed at blackstone, with error : {"summaryMessage":"Failed to capture contents","failures":[]}
    at com.vmware.vrealize.lcm.blackstone.core.task.BlackStoneBaseTask.pollPipelineRequest(BlackStoneBaseTask.java:130)
    at com.vmware.vrealize.lcm.blackstone.core.task.BlackStoneReleaseTask.execute(BlackStoneReleaseTask.java:97)
    at com.vmware.vrealize.lcm.automata.core.TaskThread.run(TaskThread.java:63)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.base/java.lang.Thread.run(Unknown Source)

• The /var/log/vrlcm/blackstone-spring.log contains an error similar to:

ERROR <FQDN> --- [pool-2-thread-5] c.v.b.p.s.PipelineRequestPostProcessor [lambda$processPipelineRequests$2] : statusMessage : [{​​ "messageId":"LCMBLACKSTONE213012","message":"LCMBLACKSTONE213012","eventId":"<event_id>","retry":false,"exceptionMessage":"Received exception while triggering pipeline action on blackstone.","exceptionStackTrace":"com.vmware.vrealize.lcm.common.exception.LcmException: Request execution failed at blackstone, with error : {​​​\"summaryMessage\":\"Failed to deploy contents\",\"failures\":[{​​​\"errorMessage\":\"Failed to deploy the content : <Content_Name> to the endpoint: <LCM_EndpointName>, Error: null\"}​​​

 

Environment

VMware Aria Suite Lifecycle 8.x

Cause

The error can occur when the content being captured contains special characters in its name. In this particular instance the issue was caused by an equals sign '=' in an Aria Operation alert definition's symptom.

Resolution

The issue is pending a resolution.

Workaround:
To workaround the issue rename the content to ensure no special characters exist. Due to how symptom id's are stored simply renaming the symptoms may not be sufficient to resolve. In these instances its necessary to copy or clone the symptom and delete the original.

Additional Information

Impact/Risks:
Capturing or deploying content via Aria Suite lifecycle fails.