VMware Communities: ESX patches - order and numbering

Up to Discussions in VI: ESX 3.0

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)

9 Replies Last post: Dec 17, 2007 8:39 AM by johnpearson

ESX patches - order and numbering

Oct 31, 2007 5:44 PM

GBromage 414 posts since
Jun 14, 2006

Hi there!

Whilst looking through the latest swag of patches, I noticed that ESX-1001907 replaces ESX-1002087, and ESX-1001905 replaces ESX-1002088. I realise that we're supposed to apply patches in date order but in most logical cases, you'd expect that the higher number patch would replace the lower number. The 8 October patches are ESX-100*20*xx and the 29 October patches are ESX-100*19*xx.

Is there some arcane logic to the patch numbering which goes far beyond my limited mental capacity?

(And, as a side note, why are the patches ESX-xxxxxx and not VI3-xxxxx?)

Cheers,

Greg

Tags: esx3, esxupdate, patch

Reply Re: ESX patches - order and numbering Oct 31, 2007 11:44 PM

virtualdud3 725 posts since
Sep 1, 2007

I don't know, man. What I wouldn't give for a "Patch Decoder Ring"...

If anyone knows the answer, I would love to hear it.

I look at it this way - knowing little things like installing patches in chronological order (as opposed to numeric order) are why I have a job!!!

###############
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

Reply Re: ESX patches - order and numbering Nov 1, 2007 8:31 AM

torontoguy 50 posts since
Feb 23, 2006

why not save yourself a lot of hassle and just use the ESX Autopatch?

Reply Re: ESX patches - order and numbering Nov 1, 2007 8:34 AM

lhedrick 78 posts since
Aug 23, 2005

I skipped all the patches and installed Update 1 instead hoping it would do until 3.5 comes out...

Reply Re: ESX patches - order and numbering Nov 1, 2007 8:42 AM

in response to: torontoguy

virtualdud3 725 posts since
Sep 1, 2007

I'm not saying that I am having any troubles patching ESX servers (I imagine the original poster isn't either).

I would simply like to delve (sp?) deeper into the logic of the "patch nomenclature". Of course, it is a simple matter to run "esxupdate info | grep Release" to determine the release date of the patch, and then write a script to ensure that they are installed in the proper order.

You also have to keep an eye-out for the wild-hair patch like ESX-6431040 that, when untarred, contains a script that installs the other seven patches contained within!!!

###############
If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

Reply Re: ESX patches - order and numbering Nov 1, 2007 8:36 AM

esiebert7625 6,786 posts since
Oct 23, 2006 Moderator

Here's some info from the VMworld presentation on patching that BrianG gave. VI3 is a suite of products that includes VirtualCenter, thats why they are called ESX-

Patches DO need to be applied in order of release date

Within the release month, order is not important

If automating patch application with scripts, care should be taken to insure proper order.

Patch release dates are clearly annotated on the VMware internal patch repository

-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-
Thanks, Eric
Visit my website: http://vmware-land.com
-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-

Reply Re: ESX patches - order and numbering Nov 1, 2007 6:00 PM

in response to: virtualdud3

GBromage 414 posts since
Jun 14, 2006

You're right - my question isn't about how to patch (I'm cool with that) or that they should be installed in date order.

I'm more concerned in why the numbering of patches doesn't have any apparent relation to the correct order. Each batch of patches seems to to be in the same numerical series, but what significance (if any) is there that the 10019xx were released after 10020xx patches. And the ones before that were 10017xx patches.

By implication, what happend to 10018xx?

Thanks,

Greg

Reply Re: ESX patches - order and numbering Dec 14, 2007 1:25 PM

johnpearson 24 posts since
Aug 15, 2006

I realize this thread is a little old, but I have another question... When a new patch supersedes an old patch, THEN what becomes the patch order. Do you still need to install the old patch first since it was released earlier, or can you skip that patch and apply the newer version further down the process ... i.e. in the following month's worth of releases. This just seems to get more confusing. (I need a patch decoder ring too! <g>) I'm using the esx-autopatch script and need to re-build my patchlist file for the Nov 30 releases, so was just wondering if I could just comment out lines in my patchlist file for patches that are no longer viable. Thanks! -John

Reply Re: ESX patches - order and numbering Dec 14, 2007 4:02 PM

in response to: johnpearson

dominic7 2,089 posts since
Jan 11, 2005

John,

You don't need to install an old patch that will get superceded later. Since you're already using the script that I developed I think I can help you out some more. I actually have a set of patchlist.txt that skip the patches that are superceded.

http://vmprofessional.com/material/3.0.2/nodups/patchlist.txt

http://vmprofessional.com/material/3.0.1/nodups/patchlist.txt

-Dominic

Reply Re: ESX patches - order and numbering Dec 17, 2007 8:39 AM

in response to: dominic7

johnpearson 24 posts since
Aug 15, 2006

Many thanks Dominic! Your patchlist looks like mine, so I must be doing it right.

FYI, I modified your script to include updating the 'hosts' file on all our ESX boxes. Since it changes a lot in our environment, I figured I might as well be able to update that too. <g> Thanks for great code!! With 55+ hosts (and growing), I don't know what I'd do without it.

I keep hoping someday VMware will get its act together as far as patching is concerned, but until then, it's nice to know the community has people like you!
John Pearson

Actions

View as PDF

Up to Discussions in VI: ESX 3.0