SDDC_SERVICE_API_CALL_FAILED error when trying to retrieve manifest file for async patch upgrade due to feature.lcm.2.0 being disabled
search cancel

SDDC_SERVICE_API_CALL_FAILED error when trying to retrieve manifest file for async patch upgrade due to feature.lcm.2.0 being disabled

book

Article ID: 431171

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer

Issue/Introduction

Unable to obtain manifest file during an async upgrade and receive the below errors 

Asyncpatch.log

2026-02-19 20:18:08.342 [ERROR] Exception thrown when uploading manifest to lcm
2026-02-19 20:18:08.343 [INFO ] Telemetry data collection is not enabled
2026-02-19 20:18:08.343 [ERROR] Error while initiating required functionality: INPUT_SPEC_WORKFLOW
2026-02-19 20:18:08.358 [ERROR] SDDC_SERVICE_API_CALL_FAILED
-- Error Message: Api call to /v1/manifests failed.


Lcm-debug.log

2026-02-04T19:46:32.653+0000 DEBUG [vcf_lcm,8852e0dc3a3a3ec8,6c7c] [c.v.evo.sddc.lcm.orch.Orchestrator,Scheduled-5] Starting orchestrating scheduled upgrades which are past due
2026-02-04T19:46:52.889+0000 WARN  [vcf_lcm,2929f288dcedfaa5,fde9] [c.v.v.f.i.FeatureInterceptor,http-nio-127.0.0.1-7400-exec-2] Feature feature.lcm.2.0 is disabled
2026-02-04T19:46:53.074+0000 WARN  [vcf_lcm,73352b3b8d0fac4e,794f] [c.v.v.f.t.i.FunctionalityToggleApiFilter,http-nio-127.0.0.1-7400-exec-3] No functionalities for POST /v1/manifests
found, call functionality toggle for unknown functionality.





Environment

VMware Cloud Foundation 5.2

Cause

The feature.lcm.2.0 parameter is set to false in one of the async patch feature.properties files and it is overriding the ability to enable the feature.

Resolution

  1. Open an SSH session to SDDC Manager and su to root
  2. Run command to find all feature.properties files

    find / -iname feature.properties

    Example Output
    root@SDDC_Manager [ ~ ]# find / -iname feature.properties 
    /nfs/vmware/vcf/nfs-mount/asyncPatchTool/conf/feature.properties 
    /opt/vmware/vcf/commonsvcs/conf/feature.properties 
    /opt/vmware/vcf/lcm/lcm-app/conf/feature.properties 
    /storage/alt_root/home/vcf/vcf-async-patch-tool/conf/fcature.propertics 
    /storage/alt root/home/vcf/feature.properties 
    /storage/alt_root/home/vcf/lcm-tools-prod/conf/feature.properties 
    /storage/alt_root/home/vcf/lcm-tools-prod-4. 4.1.1/conf/feature.properties 
    /home/vcf/feature.properties /home/vcf/conf/feature.properties 
    /home/vcf/asyncPatchTool/conf/feature.properties 
    /home/vcf/vcf-async-patch-tool/conf/feature.properties 
    /home/vcf/1cm-tools-prod/conf/feature.properties 
    /home/vcf/lcm-tools-prod-4.4.1.1/conf/feature.properties

     

  3. Update feature.lcm.2.0 property to equal false  in all async patch feature.properties files
    /nfs/vmware/vcf/nfs-mount/asyncPatchTool/conf/feature.properties
    
    /storage/alt_root/home/vcf/vcf-async-patch-tool/conf/fcature.propertics
    
    /home/vcf/asyncPatchTool/conf/feature.properties
    
    /home/vcf/vcf-async-patch-tool/conf/feature.properties

     

  4. Re-initiate manifest download using the Async Patch tool

    ./lcm-bundle-transfer-util --download --bundleManifests --depotDownloadToken download-token --bundleManifestsDir binaries_dir/bundleManifests

    Reference: Offline Download of Async Patch Bundles