VMware Cloud Community
stanj
Enthusiast
Enthusiast

ESXi VIB update fails

I tried updating our standalone ESXi 6.0 version with the latest patch and get the below error I have done many of these on ESXi 5.5 and had no issues.

I tried a new download and even changed target folders and get the same message

Is there something new in 6.0 that needs to be added?




thanks


# esxcli software vib update -d  /vmimages/ESXi600-201505001.zip [MetadataDownloadError] Could not download from depot at zip:/vmimages/ESXi600-201505001.zip?index.xml, skipping (('zip:/vmimages/ESXi600-201505001.zip?index.xml', '', 'Error extracting index.xml from /vmimages/ESXi600-201505001.zip: File is not a zip file'))         url = zip:/vmimages/ESXi600-201505001.zip?index.xml Please refer to the log file for more details.

0 Kudos
4 Replies
microkid
Hot Shot
Hot Shot

Obvious question: did you verify you can open and read the contents of the ZIP file? e.g. check if the file is not corrupt?

0 Kudos
GaneshNetworks

Run md5sum or sha1checksum against the downloaded file and make sure that it is same as below. If it is not, try to download the file again.

md5sum:

be402f101729134412e6b69235c5eec2

sha1checksum:

6228d387354c1a83f02aea556c479eaffa960210

~GaneshNetworks™~ If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
0 Kudos
UmeshAhuja
Commander
Commander

Hi,

Its seems like issue might be of below two reasons :-

  1. The full path of the specific driver and/or bundle is not specified. 
  2. The esxcli command syntax is incorrect.

To resolve this issue, ensure to use the full path to the zip bundle. 

For example, use a command similar to:

esxcli software vib install -d /vmfs/volume/datastoreUUID/FILENAME.zip

Note : To determine the Datastore UUID using the vSphere Client:

  1. Navigate to Configuration > Storage. 
  2. Select the datastore. 
  3. View Location under Datastore Details.

    The Datastore UUID appears similar to /vmfs/volumes/51dda02d-fade5016-8a08-005056171889 where 51dda02d-fade5016-8a08-005056171889 is the UUID.
Thanks n Regards
Umesh Ahuja

If your query resolved then please consider awarding points by correct or helpful marking.
BlackMoonWolf
Enthusiast
Enthusiast


  1. The full path of the specific driver and/or bundle is not specified. 

Even now - 7 years later - this solved the issue. I had to use the full, absolute path to the file. Yes. EVEN THOUGH I was in the same directory as the file! (How very pedantic!)

It's always the simple things that get ya. 🤣

Thanks!

0 Kudos