VCF Automation Power Off Fails with Error LCMVMSP10030 Due to Transient Snapshot Check Failure in VCF 9.0

Products

• VCF Automation
• VCF Operations

Issue/Introduction

When attempting to power off VCF Automation nodes via Fleet Management > Lifecycle > VCF Management > Automation > Manage > Power Off in VCF Operations 9.x, the task fails with the following error:

• Error Code: LCMVMSP10030
• Error Message: "Found snapshots on VMSP management nodes. Aborting shutdown."
• Fleet Management logs (/var/log/vrlcm/vmware-vrlcm.log) shows a response similar to the following:
  

  com.vmware.vrealize.lcm.vmsp.common.exception.RestClientException: API failed with response: {"statusCode":218,"responseMessage":"status code 218","outputData":"{\"error\":\"job failed: BackoffLimitExceeded; Job has reached the specified backoff limit\",\"statusCode\":218,\"output\":\"Found snapshots on VMSP management nodes. Aborting shutdown.\\n\",\"running\":false,\"completedAt\":\"YYYY-MM-DDTHH:MM:SSZ\"}"}
  

• verifying the nodes directly in the vSphere Client confirms that no snapshots exist.
• synthetic-checker　log on VCF Automation (~/synthetic-checker-xxxxxxxx/synthetic-checker/console-log-xxxxxx.log) returen other than　"success"  
  

  YYYY-MM-DDTHH:MM:SS.SSSZ stderr F {"level":"info","name":"checker","check":"platform-snapshots-snapshot", ... "message":"starting checks"}
  YYYY-MM-DDTHH:MM:SS.SSSZ stderr F {"level":"info","name":"server","request":{"method":"GET","uri":"/status?selector=group=snapshots", ... },"status":404,"time":"YYYY-MM-DDTHH:MM:SSZ","message":"accessed"}

  
  
  

Environment

VCF Operations 9.x

Cause

 If the internal monitoring services or Kubernetes pods within the VCF Automation appliance are restarting or temporarily unavailable (returning a 404 Not Found or timeout), the lifecycle engine may fail to confirm the "zero-snapshot" state. As a safety precaution, the system aborts the shutdown and reports that snapshots were found, even if the underlying vSphere inventory is clear.

 

Resolution

To resolve this issue, ensure the VCF Automation internal services are stable and synchronize the inventory before retrying the operation.

1. Wait for Service Stability: If any VCF Automation pods were recently restarted, wait 5–10 minutes for all services to reach a "Running" or "Healthy" state.
2. Trigger Inventory Sync:
   • Navigate to Fleet Management > Lifecycle > VCF Management > Automation > Manage.
   • Click Inventory Sync.
   • Wait for the sync task to complete successfully.
3. Retry Power Off: Once the inventory is synchronized and services are stable, initiate the Power Off task again.