Triggering Inventory sync for VCF logs component fails with error 'LCMVROPSYSTEM30018'

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Triggering inventory sync fails with error 'LCMVROPSYSTEM30018' 
• /var/log/vrlcm/vmware_vrlcm.log in Fleet Management shows the following error in the logs: 

  2026-02-02T06:08:29.441Z INFO vrlcm[1297] [pool-3-thread-37] [c.v.v.l.p.a.s.Task]  -- Injecting task failure event. Error Code : 'LCMVROPSYSTEM30018', Retry : 'true', Causing Properties : '{ CAUSE ::  }' 
  java.lang.RuntimeException: java.io.IOException: Server returned HTTP response code: 400 for URL: https://<VCFOPSPRIMARYFQDN>/casa/capabilities
   at com.vmware.vrealize.lcm.plugin.core.vrops.tasks.PushCapabilitiesToOpsTask.lambda$execute$0(PushCapabilitiesToOpsTask.java:101) ~[vmlcm-vropsplugin-core-9.0.2.0-SNAPSHOT.jar!/:?]
  Caused by: java.io.IOException: Server returned HTTP response code: 400 for URL: https://<VCFOPSPRIMARYFQDN>/casa/capabilities

• Restarting VCF Operations cluster as per KB Re-deploy of Operations for Logs fails with LCMVROPSYSTEM30018 does not resolve the issue 
• admin@local account for Fleet Management component shows as disconnected under “Fleet Management → Passwords → VCF Management”

Environment

VCF Operations 9.0.x

VCF Operations for Logs 9.0.x

Resolution

1. Apply KB admin@local account for Fleet Management component appears as disconnected 
2. Take a snapshot of VCF Operations node(s) as per documentation Create a Snapshot Before You Upgrade VCF Operations 
3. While VCF Operations cluster is offline reboot the VCF Operations virtual machines in order documented in KB Rebooting nodes in Aria Operations
4. Ensure VCF operations nodes have the hostname set correctly by running the command 

   $VMWARE_PYTHON_BIN /usr/lib/vmware-vcopssuite/utilities/bin/sethostname.py NewHostName

5. Take a snapshot of VCF operations for Logs nodes without memory without quiesce.
6. Restart the VCF operations for Logs virtual machine
7. Bring VCF operations cluster back online by navigating to https://<primary-node-FQDN-or-IP-address>/admin → Click Bring Cluster Online under the cluster status