Message: Unknown exception Personality with ID: #### not found caught when fetching cluster image with name ####Remediation Message:Reference Token: ####Cause: Personality with ID: ####-####-#### not found
yyyy-mm-ddThh:mm:ss DEBUG [vcf_dm] [c.v.e.s.o.c.c.ContractParamBuilder,dm-exec-25] Contract task Fetch the details of the Image for a given cluster input: {"personalityName":"####"}yyyy-mm-ddThh:mm:ss DEBUG [vcf_dm] [c.v.v.c.f.a.GetPersonalityDetailsAction,dm-exec-25] Getting personality details for the personality id: ####-####-####yyyy-mm-ddThh:mm:ss DEBUG [vcf_dm] [c.v.v.c.f.a.GetPersonalityDetailsAction,dm-exec-25] GetPersonalityDetailsAction attempting to get the personality.yyyy-mm-ddThh:mm:ss DEBUG [vcf_dm] [c.v.e.s.c.s.a.l.LcmPublicApiAdapterImpl,dm-exec-25] Getting details for personality with Id: ####-####-####yyyy-mm-ddThh:mm:ss DEBUG [vcf_dm] [c.v.v.c.f.a.GetPersonalityDetailsAction,dm-exec-25] GetPersonalityDetailsAction successfully got this personality: {personality_deatils_here}yyyy-mm-ddThh:mm:ss DEBUG [vcf_dm] [c.v.e.s.c.s.a.l.LcmPublicApiAdapterImpl,dm-exec-25] Getting software spec for personality with Id: ####-####-####yyyy-mm-ddThh:mm:ss ERROR [vcf_dm] [c.v.e.s.c.s.a.l.LcmPublicApiAdapterImpl,dm-exec-25] Failed to get software spec for personality with Id: ####-####-####com.vmware.cloud.foundation.rest.shared.lcm.runtime.ApiException: at com.vmware.cloud.foundation.rest.shared.lcm.runtime.ApiClient.handleResponse(ApiClient.java:788) at com.vmware.cloud.foundation.rest.shared.lcm.runtime.ApiClient.execute(ApiClient.java:708) at com.vmware.cloud.foundation.rest.shared.lcm.service.PersonalitiesInternalApi.getPersonalitySoftwareSpecificationWithHttpInfo(PersonalitiesInternalApi.java:141) at com.vmware.cloud.foundation.rest.shared.lcm.service.PersonalitiesInternalApi.getPersonalitySoftwareSpecification(PersonalitiesInternalApi.java:127) at com.vmware.evo.sddc.common.services.adapters.lcmpublicapiservice.LcmPublicApiAdapterImpl.getPersonalitySoftwareSpec(LcmPublicApiAdapterImpl.java:210) at com.vmware.vcf.clustermanager.fsm.actions.GetPersonalityDetailsAction.execute(GetPersonalityDetailsAction.java:74)yyyy-mm-ddThh:mm:ssERROR [vcf_dm] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-25] [####] GET_CLUSTER_IMAGE_DETAILS_GENERAL_EXCEPTION Unknown exception Personality with ID: ####-####-#### not found caught when fetching cluster image with name com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Unknown exception Personality with ID: ####-####-#### not found caught when fetching cluster image with name
root@sddc_fqdn [ / ]# psql -h localhost -U postgres -d lcm -c "\x" -c "select * from personality;"Expanded display is on.-[ RECORD 1 ]------------+-----------------------------------------------------------------------------personality_id | ####-####-####created_by |depot_path | /nfs/vmware/vcf/nfs-mount/personalities/####-####-####description |display_name |tags |image_checksum |image_size |kb_article |personality_name | Management-Domain-ESXi-Personalityimport_time | zip_file |add_on_name |add_on_version |base_image_version | 9.0.0.0.24755229additional_image_details | {"alternativeImages": null, "removedComponents": []}checksum |
type | SINGLE
Personality files are missing in the path /nfs/vmware/vcf/nfs-mount on SDDC Manager.
1. Take a snapshot for the SDDC manager VM.
2. Login with vcf and su to root user.
3. Run the command to check the existing personality and ensure the ID matches the name -
psql -h localhost -U postgres -d lcm -c "\x" -c "select * from personality;"
4. Run this command to delete the personality ID that gives the error during the cluster creation -
psql -h localhost -U postgres -d lcm -c "\x" -c "delete from personality where personality_id='####-####-####';"
5. Refresh the Image Management page and you should see image will no longer be present.
6. Use the Import image option, to re-create the image on the SDDC.
You should see the task vSphere Lifecycle Manager Image Upload Management-Domain-ESXi-Personality initiated from SDDC and Export image initiated from the vCenter server.
7. After the import is successful, navigate to /nfs/vmware/vcf/nfs-mount/personalities/ and check the files.
8. Re-trigger the task from SDDC manager.
This error can also occur during an ESX upgrade via VCF Operations if an image is deleted and re-downloaded after an upgrade plan has been created.
In this scenario, the operation fails during the resource validation phase with the following message:
| Resource Name | <Cluster> |
|---|---|
| Description | ESX LCM cluster commit phase orchestrator |
| Result | Failed to execute the resource validations |
|---|---|
| Remediation | Please contact Broadcom Technical Support for further assistance. |
The pre-check report will display the following error:Failed to execute the resource validations: Cannot invoke com.vmware.evo.sddc.lcm.model.personality.Personality.getSoftwareInfo() because personality is null.
This issue is caused by a personality ID mismatch between the existing upgrade plan and the new database entry in SDDC Manager. To resolve this, cancel the existing upgrade plan and recreate it to synchronize with the correct ID.