vLCM Unable to Unzip Update
search cancel

vLCM Unable to Unzip Update

book

Article ID: 429417

calendar_today

Updated On:

Products

VMware vCenter Server VMware vCenter Server 8.0

Issue/Introduction

  • Importing an update file to vLCM fails at 20% with below error (subfolder names in /storage/updatemgr/patch-store-temp and /tmp are random here, so will vary)
    • "A general system error occurred: Uploading offline patches task failed while creating offline depot. Error: 'integrity.fault.FileUploadInvalidPackage: Cannot upload file, because it is an invalid package. Failed to unzip package:/storage/updatemgr/patch-store-temp/vum301208313123967075.zip to /tmp/offlineBundlep0zApTstatus 2'.
  • The ZIP file can successfully upload, but fails to unzip in vCenter.
  • In /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log you see a 7zip error as below.
    • 2026-01-27T14:07:30.808-05:00 info vmware-vum-server[10707] [Originator@6876 sub=DownloadOfflinePatchTask.DownloadOfflinePatchTask{595}] [downloadOfflinePatchTask 137] Upload offline bundle: /storage/updatemgr/patch-store-temp/vum2267636
      435308604863.zip^M
      2026-01-27T14:07:30.869-05:00 error vmware-vum-server[10707] [Originator@6876 sub=miscUtil] [miscUtilPosix 827] Error in 7z command: ^M
      2026-01-27T14:07:30.869-05:00 error vmware-vum-server[10707] [Originator@6876 sub=miscUtil] [miscUtilPosix 862] Failed to unzip package: /storage/updatemgr/patch-store-temp/vum2267636435308604863.zip to /tmp/offlineBundleMAjNbRstatus 2^M

Environment

vCenter 8.0

Cause

When the ZIP header is interacted with, for example a firewall unzipping and rezipping it, this can result in the ZIP header no longer being recognizable in vCenter. The contents of the ZIP are still fine, however the compressed file is no longer usable.

Resolution

  1. Extract the ZIP file.
  2. Recompress as a ZIP file using 7ZIP (vCenter specifically uses 7zip, though you may have success with other tools).
  3. Import the new ZIP file to vLCM.

Additional Information

When testing whether a package is a valid update on a computer outside the issue, you will need access to the download source. Testing with the same downloaded file that previously failed will still result in an error since you are testing with a ZIP header that has already been interacted with.