Error: "Failed to validate the checksum of VIB" due to checksum differences when remediating cluster
search cancel

Error: "Failed to validate the checksum of VIB" due to checksum differences when remediating cluster

book

Article ID: 377474

calendar_today

Updated On:

Products

VMware vCenter Server 7.0 VMware vCenter Server 8.0

Issue/Introduction

Cluster / ESXi remediation fails with the below error message using vLCM: 

"Failed to validate the checksum of VIB '/tmp/offlineBundle6lcz9d/vib20/HPE-Storage-psp/HPE_bootbank_HPE-Storage-psp_7.0.2-#####.vib', because the computed checksum differs from the expected one stored in metadata. Make sure the specified VIB is NOT corrupted and the expected checksum stored in metadata is correct."

/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log on the vCenter server 

YYYY-MM-DDTHH:MM:SS info vmware-vum-server[4050245] [Originator@6876 sub=DownloadMgr opID=afbc4aed-####-45ce-982c-962e1bd9e19d] [downloadMgr 671] Executing download job {140324976072944}, url=/tmp/offlineBundle6lcz9d/vib20/HPE-Storage-psp/HPE_bootbank_HPE-Storage-psp_7.0.2-#####.vib
YYYY-MM-DDTHH:MM:SS  error vmware-vum-server[4050245] [Originator@6876 sub=utilPosix opID=afbc4aed-####-45ce-982c-962e1bd9e19d] [utilPosix 358] Unexpected failure for filesystem::copy_file(): No such file or directory
YYYY-MM-DDTHH:MM:SS error vmware-vum-server[4050245] [Originator@6876 sub=DownloadMgr opID=afbc4aed-####-45ce-982c-962e1bd9e19d] [downloadMgr 712] Executing download job {140324976072944} throws error: Unexpected failure for filesystem::copy_file(): No such file or directory
YYYY-MM-DDTHH:MM:SS  error vmware-vum-server[4050245] [Originator@6876 sub=HostUpdateDepotManager opID=afbc4aed-####-45ce-982c-962e1bd9e19d] [vibDownloaderImpl 234] Computed checksum: 74fa3e1c9942b7a179820e9f78bc1c352fc98f8414cc4f8898d3d61e5297ab18 of file: /storage/updatemgr/patch-store/hostupdate/Nimble/vib20/HPE-Storage-psp/HPE_bootbank_HPE-Storage-psp_7.0.2-#####.vib differs from the expected checksum: cfced43654ab3de397a0042f7cd73c71c1b343695253ab9f78f230386fc002e8
YYYY-MM-DDTHH:MM:SS  error vmware-vum-server[4050245] [Originator@6876 sub=DownloadMgr opID=afbc4aed-####-45ce-982c-962e1bd9e19d] [downloadMgr 813] Download failed for url: /tmp/offlineBundle6lcz9d/vib20/HPE-Storage-psp/HPE_bootbank_HPE-Storage-psp_7.0.2-#####.vib

Note: The issue is not exclusive to `HPE_bootbank_HPE-Storage-psp_7.0.2-#####.vib`. It can occur with any manually uploaded driver in the vLCM offline depot, such as `NetappNasPlugin`, among others. The provided snippets are for reference only.

Cause

The package such as "HPE-Storage-psp" in the offline depot is either corrupted or not fully uploaded, resulting in a checksum error

Resolution

  1. To resolve the issue, follow the below steps to remove the problematic package from the offline depot using the below steps : 
     
     
  2. Review all vLCM clusters where the component `"HPE_NimbleConnectionManagement": "7.0.2-HPE.7.0.2.0.0.#####"` has been added to the desired state/ add-on and remove it if present.
     
     
  3. Access the vCenter Server via SSH and log in as the root user.
     
     
  4. Go into appliance shell with command appliancesh and use root password.
    1. Execute the following `dcli` commands to list and identify the offline depot.
       
       
    2. List offline depots
      dcli com vmware esx settings depots offline list
                  If prompted for credentials, use the administrator account. This gives the offline depots and their summary info. Identify the offline depot of NimbleConnectionManagement.
       
       
    3. List offline depot content to make sure which one to delete:
      dcli com vmware esx settings depots offline content get --depot <depot UUID>
       
       
    4. Delete the offline depot which is causing the issue 
      dcli com vmware esx settings depots offline delete-task --depot <depot UUID>
       
       
  5. The command in 4.3 returns the delete task id, you can check the task result using the command:
          dcli com vmware cis tasks get --task <task ID from 4.3>
     
     
     
  6. Once the task is completed successfully, upload the offline depot again to the vLCM.
     
     
  7. Add the component back to the desired state of the cluster.
     
     
  8. Remediate the cluster.  
               If remediation fails with an error indicating that the VIB cannot be found, restart all vCenter services or reset the vCenter Server and retry cluster / ESXi remediation.
Powered by Wolken Software