ESX 350 esxupdate - patch requires "3.5.0-6460"

[vitielj]

Started with a clean install of ESX 3.5. Using esxupdate to patch the system. Several issues:

A). contents.xml file on page this am 11/13/08 - has the older 2007 bundles in it - not just the 2008 bundles that superseded them.

b). ran esxupdate for patch esx350-200802403 ok then rebooted. Try to run ESX350-20082409 that many other patches needed. Got an error that this patch requires http://'3.5.0-6460* but that bundle can not be found. Where is this bundle so that it can be installed.

Thanks,

Joe

[smudge1977]

I have only been running 3.5 in my lab but the update manager seems to handel all patches just fine without haveing to go to the command prompt

I would recomend doing things that way based on this....

[azn2kew]

As of March 10, 2008 there are 18 new patches for ESX 3.5 and they should superceded previous released: Looking at the patches I don't see anything about "3.5.0-6460" even googling didn't come any close to it. Can you submit a screenshot of the error to see what's that about.

Patches for March 10, 2008

NOTE: VMware has discovered an issue that, under very specific conditions, might inhibit certain patches from being applied to ESX Server 3.5 hosts. The issue is fixed in the patch release for March 10, 2008. All the bundles released January 17 have been superseded by the bundles released for March 10, 2008 and the bundles for January 17, 2008 are no longer available.

Regards,

Stefan Nguyen

"The Power of Knowledge"

[azn2kew]

There are several good patching tools out there like VMTS.net, shell script patching tools, Updates Manager and VI3 Patch Downloader 2 and might be others. I've found using scripting tools is faster and easier. All you do is upload all the patches to /var/updates and run the script and go out for a coffee 30 minutes come back reboot your esx host than you're done. Michael Knight has great script that does it really well.

Regards,

Stefan Nguyen

"The Power of Knowledge"

[vitielj]

This is my execution attempts with esxupdate.

# esxupdate -b ESX350-200802409-BG update

INFO: No depot URL specified, going with

INFO: Configuring...

ERROR: is already installed, nothing for esxupdate to do.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

# esxupdate --test update

INFO: No depot URL specified, going with

INFO: No -b specified, selecting all bundles in depot.

INFO: Configuring...

ERROR: requires http://'3.5.0-6460*' but these bundles cannot b e found. Please make sure they are in the depot and specified in the bundle list .

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

is already installed, nothing for esxupdate to do.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires ESX350-200802409-BG, but it is not applicable.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires ESX350-200802409-BG, but it is not applicable.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires ESX350-200802409-BG, but it is not applicable.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires ESX350-200802409-BG, but it is not applicable.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires ESX350-200802409-BG, but it is not applicable.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires ESX350-200802409-BG, but it is not applicable.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

requires http://'3.5.0-6460*' but these bundles cannot be foun d. Please make sure they are in the depot and specified in the bundle list.

Thanks for the help in advance,

JOe

[azn2kew]

esxupdate -n -r http://<yourservername>:8082/ESX-$item update"; (I don't know http* error relate to the -r switch but you can give it a try. You have -b switch that I'm not familiar. (options -v -r -l -x -U -n -f ) etc...don't see -b please specify what is -b for my own knowledge!

Regards,

Stefan Nguyen

"The Power of Knowledge"

[petedr]

You had posted the web had the wrong contents file. Seems like it has been hit or miss but I was able to download it.

Attaching the 3/10 file it if you need it.

[vitielj]

That is the same one that I have dated - 3/6/2008.

It has bad contents... - as it should not have the 2007 files in it.

<contents createdTimestamp="1204852670" id="1204852670.44-0.885413748532" version="1.0"> <folder bundleID="ESX350-200712401-BG" name="ESX350-200712401-BG" /> <folder bundleID="ESX350-200712402-SG" name="ESX350-200712402-SG" /> <folder bundleID="ESX350-200712403-SG" name="ESX350-200712403-SG" /> <folder bundleID="ESX350-200712404-SG" name="ESX350-200712404-SG" /> <folder bundleID="ESX350-200712405-SG" name="ESX350-200712405-SG" /> <folder bundleID="ESX350-200712406-BG" name="ESX350-200712406-BG" /> <folder bundleID="ESX350-200712407-BG" name="ESX350-200712407-BG" /> <folder bundleID="ESX350-200712409-BG" name="ESX350-200712409-BG" /> <folder bundleID="ESX350-200712410-BG" name="ESX350-200712410-BG" /> <folder bundleID="ESX350-200802301-BG" name="ESX350-200802301-BG" /> <folder bundleID="ESX350-200802303-SG" name="ESX350-200802303-SG" /> <folder bundleID="ESX350-200802304-SG" name="ESX350-200802304-SG" /> <folder bundleID="ESX350-200802305-SG" name="ESX350-200802305-SG" /> <folder bundleID="ESX350-200802306-BG" name="ESX350-200802306-BG" /> <folder bundleID="ESX350-200802401-BG" name="ESX350-200802401-BG" /> <folder bundleID="ESX350-200802403-BG" name="ESX350-200802403-BG" /> <folder bundleID="ESX350-200802404-BG" name="ESX350-200802404-BG" /> <folder bundleID="ESX350-200802405-BG" name="ESX350-200802405-BG" /> <folder bundleID="ESX350-200802406-SG" name="ESX350-200802406-SG" /> <folder bundleID="ESX350-200802408-SG" name="ESX350-200802408-SG" /> <folder bundleID="ESX350-200802409-BG" name="ESX350-200802409-BG" /> <folder bundleID="ESX350-200802410-BG" name="ESX350-200802410-BG" /> <folder bundleID="ESX350-200802411-BG" name="ESX350-200802411-BG" /> <folder bundleID="ESX350-200802412-BG" name="ESX350-200802412-BG" /> <folder bundleID="ESX350-200802413-BG" name="ESX350-200802413-BG" /> <folder bundleID="ESX350-200802414-BG" name="ESX350-200802414-BG" /> <folder bundleID="ESX350-200802415-SG" name="ESX350-200802415-SG" /> </contents>

Joe

[petedr]

I was able to patch my 3.5 host without any issue using that contents file. I created a march patch directory and unzipped all 18 patches in that directory along with unzipping the contents file.

Then did :

esxupdate --test update ( to verify the patches )

then

esxupdate update ( it applied all 18 patches and then I rebooted ).

[Saju_C]

Hi

Are you trying to patch the machine using a HTTP depot?

Can you download all the patches and contents.zip again and try the below method for applying the patches.

Copy all the patches and contents.zip to a directory in ESX (say /var/updates). Unzip all the patches and contents.zip.

Use "esxupdate -d <the_directory_where_patches_are_loacted> -b <the_specific_bundle> update Eg:- esxupdate -d /var/updates -b /var/updates/ESX350-200802409-BG update

Stefan Nguyen : -b is used to patch the machine with a specific patch bundle . I think -b is a new option introduced in ESX 3.5 along with -d option.

Thanks

Saju

[Saju_C · Accepted solution]

Hi Joe

I had a chance to patch one ESX machine now and tried your scenario during patching. The machine was a fresh ESX 3.5 machine. First applied the ESX350-200802403-BG patch and rebooted the machine. .

# esxupdate -l query

Installed software bundles:

-

---

Name -

---

--- Install Date --- --- Summary ---

3.5.0-64607 05:54:14 03/13/08 Full bundle of ESX 3.5.0-64607

ESX350-200802403-BG 22:27:58 03/13/08 Improved Data Collection for vm-support.

Then applied the next patch ESX350-200802409-BG

# esxupdate -b ESX350-200802403-BG update

INFO: No repository URL specified, going with file:///root/patches/ESX350-200802403-BG

INFO: Configuring...

INFO: Preparing to install ...

INFO: Downloading VMware-esx-scripts-3.5.0-80578.i386.rpm...

INFO: Checking disk space and running test transaction...

INFO: Pre-installing http://'VMware-esx-scripts.i386'...

INFO: | Gathering header information file(s) from server(s)

INFO: | Server: Bundle ESX350-200802403-BG

INFO: | Finding updated packages

INFO: | Downloading needed headers

INFO: | VMware-esx-scripts-0-3.5. 100% |=========================| 5.8 kB 00:

INFO: | Resolving dependencies

INFO: | Dependencies resolved

INFO: | I will do the following:

INFO: |

INFO: | Downloading Packages

INFO: | Getting VMware-esx-scripts-3.5.0-80578.i386.rpm

INFO: | Running test transaction:

INFO: | Test transaction complete, Success!

INFO: | VMware-esx-scripts 100 % done 1/2

INFO: | Completing update for VMware-esx-scripts - 2/2

INFO: | Updated: VMware-esx-scripts 3.5.0-80578.i386

INFO: | Transaction(s) Complete

INFO: Pre-install packages up-to-date

INFO: Restarting /usr/sbin/esxupdate...

INFO: Configuring...

INFO: Preparing to install ...

INFO: The following RPMs are already installed on the system and will be skipped

INFO: Checking disk space and running test transaction...

INFO: Running esxcfg-boot to regenerate initrds...

INFO: --- TOTALS: 1 packages installed, 0 pending or failed, 0 removed, 0 excluded ---

INFO: Install of succeeded.

# reboot

Things look fine to me. Please download the patches again and try patching the machine.

Thanks

Saju