VCF Installer Fails at "Deploy and configure NSX" subtask 'Upload Personality to SDDC Manager'
search cancel

VCF Installer Fails at "Deploy and configure NSX" subtask 'Upload Personality to SDDC Manager'

book

Article ID: 442239

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer

Issue/Introduction

When deploying VMware Cloud Foundation (VCF) using the VCF Installer, the process fails during the Deploy and configure NSX task at the subtask Upload Personality to SDDC Manager.

  • The VCF Installer UI displays the error: Failed to upload personality to SDDC Manager.
  • The /var/log/vmware/vcf/lcm/lcm.log on the SDDC Manager contains the following error sequence: ERROR [vcf_lcm] [c.v.e.s.l.s.i.PersonalityUploadAsyncHandler] Error while updating software info in personality. Details : java.lang.RuntimeException: java.lang.ClassNotFoundException: com.vmware.cis.SessionStub

Environment

  • Product: VMware Cloud Foundation (VCF)
  • Component: SDDC Manager / VCF Installer
  • Versions: 5.x, 9.x

Cause

The failure is caused by a java.lang.ClassNotFoundException: com.vmware.cis.SessionStub within the LifeCycle Manager (LCM) service. The service fails to correctly initialize the vAPI bindings required to communicate with vCenter for exporting and uploading the ESXi image personality. This is typically a transient state issue within the service's runtime environment.

Resolution

To resolve this issue, restart the LCM service on the SDDC Manager appliance to force a reload of the required classes and service context.

  1. Log in to the SDDC Manager appliance via SSH as the vcf user.

  2. Switch to the root user:

    su -
  3. This command will make changes to your system. Review it carefully before running.

    systemctl restart lcm
  4. Review this command before running it. Monitor the service health until it is fully initialized. Use the following command to check the service status:

    curl localhost/lcm/about

    Wait until the command returns a successful JSON response (HTTP 200). Initially, you may see "Bad Gateway" errors while the service is starting up.

  5. Once the LCM service is healthy, navigate back to the VCF Installer and Retry the failed workflow.