vRSLCM deployment fails immediately with error: "Preparation for VMware Aria Suite Lifecycle deployment has failed"
search cancel

vRSLCM deployment fails immediately with error: "Preparation for VMware Aria Suite Lifecycle deployment has failed"

book

Article ID: 398060

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

  • Deploying vRealize Suite Lifecycle Manager from SDDC Manager fails very early and does not complete validation stage.
  • You will see entries in the domainmanager.log similar to:
2025-05-19T10:58:46.147+0000 ERROR [vcf_dm,681423e5370e9a51d49dde7a848,dad7] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-17]  [KAHRII] VRSLCM_DEPLOYMENT_PREPARATION_FAILED Preparation for VMware Aria Suite Lifecycle deployment has failed com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Preparation for VMware Aria Suite Lifecycle deployment has failed
        at com.vmware.evo.sddc.vrealize.services.PrepareVrslcmValidation.execute(PrepareVrslcmValidation.java:44)
        at com.vmware.evo.sddc.vrealize.services.PrepareVrslcmValidation.execute(PrepareVrslcmValidation.java:25)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:62)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:159)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:144)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:400)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:520)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:124)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:568)
        at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:85)
        at com.google.common.eventbus.Subscriber.lambda$dispatchEvent$0(Subscriber.java:71)
        at com.vmware.vcf.common.tracing.TraceRunnable.run(TraceRunnable.java:59)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.RuntimeException: POST request failed with: {"errorCode":"VCF_RUNTIME_ERROR","arguments":[],"message":"Something went wrong. Please retry or contact the service provider and provide the reference token."}

Environment

VCF 5.x
vRSLCM 8.x

Cause

This is caused by a mismatch between the vCenter FQDN stored in SDDC Manager and the output of the "hostname -f" command run directly on the vCenter. 

If you run an upgrade precheck on the Management Workload Domain you will see this failure: "Could not find VM with address to verify free space on path '/'"

Resolution

Change the vCenter hostname to match the case as seen in SDDC Manager.

  1. Take offline snapshots of all vCenters in ELM. 
  2. Log into vCenter via SSH as root.
  3. Run this command to update the vCenter hostname:
    > /opt/vmware/share/vami/vami_config_net
  4. Verify that the hostname has been updated:
    > /usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost

Additional Information

Powered by Wolken Software