VCF Upgrade fails with "Failed to find bundle manifest json for bundleID"

Products

• VMware SDDC Manager

Issue/Introduction

• After uploading an offline bundle using the Offline Bundle Transfer Utility, you try to initiate the upgrade.  
• /var/log/vmware/vcf/lcm/lcm-debug.log will report that a specific bundle is not available when the upgrade fails:
  YYYY-MM-DDTHH:MM:SS.###+#### ERROR [vcf_lcm,################,####] [c.v.e.s.l.d.c.b.BundleClientImpl,http-nio-127.0.0.1-7400-exec-5] Failed to find bundle manifest json for bundleId ########-####-####-####-############

Environment

• VCF upgrades using offline bundle transfer utility
• Upgrade from 4.x to 5.x

Cause

• Navigating to a specific domain -> Available updates -> select Cloud Foundation 5.#.#.#  -> the uploaded upgrade does not show as an option to initiate.
• The offline bundle transfer utility ignores the config drift bundle for an unknown reason.
• Verify the LCM DB for the uploaded bundles.

psql -U postgres -h localhost -d lcm -c "select upload_id,bundle_id,start_time,end_time,status from bundle_upload;"


• It will not list the drift bundle.
  • The bundle IDs can be obtained from KB VMware Cloud Foundation - Upgrade Bundle Details.
    


Resolution

Create a custom bundle spec for the drift bundle and patch it using API explorer -

1. Verify the specific location of the files listed below for the drift bundle.
   
   
2. Make sure the tar, manifest, and minifest.sig files and their parent directory have permissions set.
   1. Ex: chmod 777 -R 5.2.0-bundles
      
      
3. Navigate to API explorer.
   1. SDDC UI
   2. Developer Center
   3. API Explorer
   4. API for managing bundles
   5. v1/bundles (POST)
      
      
4. POST the custom bundle spec.

 

Sample custom bundle spec:

{
"bundleFilePath": "/nfs/vmware/vcf/nfs-mount/5.2.0-bundles/bundles/bundle-111777.tar",
"manifestFilePath": "/nfs/vmware/vcf/nfs-mount/5.2.0-bundles/manifests/bundle-111777.manifest",
"signatureFilePath": "/nfs/vmware/vcf/nfs-mount/5.2.0-bundles/manifests/bundle-111777.manifest.sig",
"compatibilitySetsFilePath": "",
"partnerExtensionSpec": {
"partnerBundleVersion": "",
"partnerBundleMetadataFilePath": ""
}
}