Error: [Errno 2] No such file or directory: /storage/updatemgr/software-update#####/stage/update/patching_backup_config.json - vCenter Server Appliance

Products

• VMware vCenter Server

Issue/Introduction

• vCenter Server updates may fail during the staging phase when using an ISO file, particularly in standalone or offline environments. This is often caused by corrupted or incomplete ISO files leading to package extraction failures.
• Update fails at approximately 9% progress.
• The VAMI or logs report: Installation Failed [Errno 2] No such file or directory: '/storage/seat/.../patching_backup_config.json' or /storage/updatemgr/.../patching_backup_config.json.
• In /var/log/vmware/applmgmt/update_microservice.log, you may see: YYYY-MM-DD HH:MM:SS, - 36754 - rpmfunctions:: isChecksumValid: 356 - ERROR - Checksum does not match, expected [####], found [####]

Environment

• VMware vCenter Server 8.0.X
• VMware vCenter Server 7.0.X
• Linux-based systems for ISO verification

 

Cause

An ISO checksum mismatch occurs when the downloaded patch file is corrupted due to network drops, storage issues, or incomplete downloads. The staging engine aborts the process before creating the required patching_backup_config.json file.

Resolution

1. Check for Checksum Errors in Logs
   • Access the vCenter Server Appliance via SSH as the root user.
   • Review the update microservice log for checksum-related errors:
     

     grep -i checksum /var/log/vmware/applmgmt/update_microservice.log

2. Look for error messages similar to:
   • "Checksum mismatch detected"
   • "SHA256 verification failed"
   • "File integrity check failed"
     
     
3. Obtain Correct Checksum Value
   • Visit the official VMware/Broadcom download page for your vCenter version.
   • Locate the checksum information (usually SHA256) provided alongside the ISO download.
   • Record the official checksum value for comparison.
     
     
4. Verify ISO Checksum
   • Navigate to the directory containing the upgrade ISO file.
   • Calculate the SHA256 checksum of your ISO file:

     sha256sum /path/to/vcsa-upgrade.iso

      Example:
     

     sha256sum /tmp/VMware-VCSA-all-8.0.2-22617221.iso

   • Compare the calculated checksum with the official checksum from the VMware/Broadcom download page.
     
     
5. Resolve Checksum Mismatches

If checksums do not match:

• • Delete the corrupted ISO file:
    

    rm /path/to/vcsa-upgrade.iso

  • Re-download the ISO file from the official Broadcom download portal.
  • Verify the new download using the checksum verification process above.
  • Ensure the checksums match before proceeding with the upgrade.

If checksums match:
   
The ISO file is valid and the issue may be related to other factors
Proceed with other troubleshooting steps for the upgrade failure

• • Additional Verification Steps
    • Check available disk space to ensure sufficient room for the upgrade:
      

      df -h

    • Verify file permissions on the ISO:

      ls -la /path/to/vcsa-upgrade.iso

    • Test ISO integrity by attempting to mount it:

      mkdir /tmp/iso_test
      mount -o loop /path/to/vcsa-upgrade.iso /tmp/iso_test
      ls /tmp/iso_test
      umount /tmp/iso_test

Additional Information

• Always use the official Broadcom download portal for ISO files
• SHA256 is the standard checksum algorithm used for VMware ISO verification
• Large ISO files may take several minutes to calculate checksums
• Consider using download managers or resume-capable tools for large ISO downloads to prevent corruption