SDDC Manager 4.x upgrade fails on "PERSONALITY_UPLOAD_NOT_FOUND"
search cancel

SDDC Manager 4.x upgrade fails on "PERSONALITY_UPLOAD_NOT_FOUND"

book

Article ID: 319906

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

  • Below errors are seen in the /var/log/vmware/vcf/lcm/lcm-debug.log location :-

    YYYY-MM-DDTHH:MM:SS.Z ERROR [vcf_lcm,e1#######4f,8575] [c.v.e.s.l.f.p.ExportedPersonalityParser,http-##-[IP]-7400-exec-2] LCM Personality json file is not found in the provided personality dir:/nfs/vmware/vcf/nfs-mount/personalities/36#######be. Only one json file is expected in the directory.|
    YYYY-MM-DDTHH:MM:SS.Z ERROR [vcf_lcm,e1#######4f,8575] [c.v.v.l.r.a.c.i.InternalTaskAssemblers,http-##-[IP]-7400-exec-2] Error occurred assigning task name for the task id: 81#######39
    com.vmware.evo.sddc.lcm.model.error.LcmException: Invalid directory provided /nfs/vmware/vcf/nfs-mount/personalities/36#######be

  • Below errors are seen in the /var/log/vmware/vcf/lcm/lcm.log location :-

    YYYY-MM-DDTHH:MM:SS.Z ERROR [vcf_lcm,e1#######4f,8575] [c.v.e.s.l.f.p.ExportedPersonalityParser,http-##-[IP]-7400-exec-2] Personality directory:/nfs/vmware/vcf/nfs-mount/personalities/36#######be doesn't exist and hence populating hardware and additional metadata failed

Environment

VMware Cloud Foundation 4.x

Cause

The database has a stale record for a specific Image Personality, but the actual files are missing from the /nfs/vmware/vcf/nfs-mount/personalities/ directory, causing the upgrade to fail.

Resolution

Use the personalities API to identify and delete the problematic ID - Personalities APIs | VMware Cloud Foundation API

Alternatively, contact Broadcom GS for assistance for deleting personality from SDDC Manager database.