Content Management Failures

Products

• VMware Aria Suite

Issue/Introduction

VMware Aria Orchestrator Content Captures fail after

• Upgrading Aria Suite Lifecycle from 8.16 to 8.18.0
• Installing Aria Suite Lifecycle 8.18.0
• Applying Product Support Pack, post Patch 1 install

Errors similar to this may be seen in /var/log/vrlcm/blackstone-spring.log:

2025-02-05 17:18:09.446 ERROR YourVRSLCMServer.example.com --- [ContentAsync-23] c.v.b.m.s.AsyncCaptureStageExecutor      [executeSingleCaptureRequest] : [Capture failure: ] Content Capture failed for [OrchestratorPackageName/com.genericExample] [v6] from end-point ExampleEndPointName with error find: ‘/opt/vmware/vlcm/blackstone/vco-cli/*’: No such file or directoryExport Failed

Error Code: LCMBLACKSTONE213006

‘Received exception while triggering pipeline action on blackstone.’

 

 

 

Environment

VMware Aria Suite Lifecycle 8.18.0

Cause

Latest updates to vcocli, including JDK enhancements

Resolution

• If the LCM is on 8.18 without any pspak applied:
  • just apply patch 1

 

• If the LCM is on 8.18 patch 1 and applied pspak on top of it
  • Create 8.16.0 folder under /opt/vmware/vlcm/blackstone/vco-cli/
  • Copy vco-cli-java-8.16.0.jar attached file to the folder(8.16.0) created above.
    • Apply correct permissions for jar file and 8.16.0 folder:.

      chmod 770
      chown root

• If the LCM is on version 8.18 and no patches or PSPAK are to be applied.
  • Take the attached file 'vco-cli-java-8.16.0.jar,' rename it to '8.18.0,' and place it under the '/opt/vmware/vlcm/blackstone/vco-cli/8.18.0' folder.
    • Apply same permissions for jar file that was on the previous jar.

      chmod 770
      chown root

Additional Information

Please see attached JAR file to replace with resolution steps