VMware Aria Operations for Logs environment creation fails with Error Code: LCMVRLISYSTEM45022

Products

• VMware vRealize Suite Lifecycle Manager 8.x

Issue/Introduction

• Below error appears in Aria Suite Lifecycle during the deployment failure or attempting the 'RETRY' Operation for the failed Aria Operations For Logs deployment: 

Error Code: LCMVRLISYSTEM45022 Unknown error (VMware Aria Operations for Logs). Unknown error (VMware Aria Operations for Logs)

 

• Below snippets will be logged in Aia Suite Lifecycle Manager:

/var/log/vrlcm/vmware_vrlcm.log 

 INFO vrlcm[1135] [pool-3-thread-22] [c.v.v.l.d.v.InstallConfigureVRLI]  -- Return message for Vmware Aria Operations for Logs for joining worker node: {"errorMessage":"This call isn't allowed after the Operations for Logs server is bootstrapped"}
 INFO vrlcm[1135] [pool-3-thread-22] [c.v.v.l.d.v.InstallConfigureVRLI]  -- Return status code for VMware Aria Operations for Logs: 409
 ERROR vrlcm[1135] [pool-3-thread-22] [c.v.v.l.d.v.InstallConfigureVRLI]  -- VRLI Join request failed with status code 409

..

2026-05-12T15:04:33.101Z INFO vrlcm[1135] [pool-3-thread-22] [c.v.v.l.p.v.AddVRLINodeToMasterNodeTask]  -- VMware Aria Operations for Logs instance is up and running
2026-05-12T15:04:33.101Z INFO vrlcm[1135] [pool-3-thread-22] [c.v.v.l.p.v.AddVRLINodeToMasterNodeTask]  -- Worker node initialized successfully
2026-05-12T15:04:33.110Z ERROR vrlcm[1135] [pool-3-thread-22] [c.v.v.l.p.v.AddVRLINodeToMasterNodeTask]  -- Exception while adding VMware Aria Operations for Logs worker to master
java.lang.NullPointerException: null
..
2026-05-12T15:04:33.115Z INFO vrlcm[1135] [pool-3-thread-22] [c.v.v.l.p.a.s.Task]  -- Injecting task failure event. Error Code : 'LCMVRLISYSTEM45022', Retry : 'true', Causing Properties : '{ CAUSE ::  }'
java.lang.NullPointerException: null

 

• Aria Operations for Logs Primary and Worker nodes may be successfully deployed and configured in the Aria Operations for Logs Cluster:

 

Environment

Aria Operations For Logs 8.18.6

Aria Suite Lifecycle Manager 8.18 SP5

Cause

During the Aria Operations for Logs deployment, Operations for Logs Worker Node gets bootstrapped.

It signifies that the application services are active and the node has moved beyond its "first-boot" or factory-reset deployment phase. Hence its unable to receive any further configuration from the Primary node during the cluster join process.

Resolution

If Aria Operations for Logs Primary and Worker nodes are successfully deployed then you can either import the existing environment in the Aria Suite Lifecycle or Redeploy the same environment.

 

• To import the existing environment in the Aria Suite Lifecycle, kindly refer this Technical documentation: Import a VMware Aria Operations for Logs environment

•  If you don't want to import the existing Aria Operations for Logs Environment in Aria Suite Lifecycle Manager, follow below steps to redeploy the Aria operations for Logs environment:

  - Shutdown existing Master and Worker nodes

  - Disconnected the Master and Worker Node VMs from network (using VM Edit settings in vSphere Client)

  - Rename Master and Worker Node VMs to "-OLD" using vSphere Client

  - Delete the FAILED Aria Operations for Logs Environment from Aria Suite Lifecycle Manager

- Now, proceed creating the new Aria Operations for Logs Environment with same configuration in Aria Suite Lifecycle Manager and monitor the deployment progress.