VMware Cloud Community
rex___co
Contributor
Contributor
Jump to solution

Applying 3.5 patches after upgrading from 3.0.2 to 3.5 with the Feb 16th 2008 3.5 Release (64607)

I upgraded my 3.0.2 servers this morning without incident. I used a nfs depot located on a win2k3 system running NFS services for Windows.

I assumed that the patches for 3.5 would still be valid to apply after applying the 3.5 update that was re-released on 2/16/2008.

Yes, i'm aware that one might assume that the patches from Jan 17th might be included in the Feb 16 release, however there is no mention of this that i was able to find.

Upon attemping to apply each patch, all reported that they were deprecated except for the security fix for Samba: ESX350-2007012402-SG

I dont know if this was an oversight in the release or a valid patch, but I have applied it on both machines. Can someone at VMWare Support please comment on this?

Tags (4)
0 Kudos
1 Solution

Accepted Solutions
jyothim
VMware Employee
VMware Employee
Jump to solution

Rex,

We have already on top of the problem... We could recreate it and are looking into the issue. You can expect the resolution ASAP.

-Jyothi

View solution in original post

0 Kudos
15 Replies
jyothim
VMware Employee
VMware Employee
Jump to solution

Hi,

There should not be any such problem that you have encountered. I am from the ESX-3.5 Patches team and we have tested this path and is successful in our environment. I would like to know more about your setup. The one that got released is not ESX-3.5 Update. It is just a re-spin to existing ESX-3.5 which got released in October. So, all the patch bundles starting from Jan can be applied on this ESX-host. Can you please verify the patch bundles md5sum as against the one in the VMware-download site? Or could you please re-configure your NFS share and download a fresh set and try again? I dont think we have any such problems. If you can recreate this problem, then you can talk to support, who can take this forward.

Thanks & Regards,

Jyothi

0 Kudos
Saju_C
VMware Employee
VMware Employee
Jump to solution

Hi Rex

Could you please let me know the build number of 3.0.2 while upgrading to 3.5GA. Which all patches for 3.0.2 were applied while you tried to upgrade? It would be great if you can provide the esxupdate -l query output.

I have recently downloaded the 3.5 GA (re-released one) and was able to upgrade 3.0.2 to 3.5 and was able to apply all the January patches.

Thanks

Saju

0 Kudos
rex___co
Contributor
Contributor
Jump to solution

before applying all patches from the following page, md5sum's were successfully verified.

http://www.vmware.com/download/vi/vi3_patches_35.html

0 Kudos
rex___co
Contributor
Contributor
Jump to solution

Hi Saju,

I dont have the build number of the 3.0.2 release that i had been running for the previous 290 days, however here is the output of `esxupdate -l query` before the update was attempted:

Wed Feb 13 15:57:58 PST 2008

-


Installed software bundles:

-


Name -


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

3.0.1-32039 11:51:40 04/25/07 Full 3.0.1 release of VMware ESX Server

ESX-1006511 10:13:56 04/27/07 Fixing TX hang in 80003ES2LAN Controller

ESX-9986131 10:26:37 04/27/07 Updated openssh, python, and openssl

ESX-8173580 10:35:07 04/27/07 Fix COS Oops running Dell OM5 w/ QLogic

ESX-6921838 10:43:29 04/27/07 hot removal of a virtual disk thru SDK

ESX-2066306 11:01:57 04/27/07 Patch for VM crashes and possible freeze

ESX-5497987 11:11:59 04/27/07 Fixes a misleading locking message.

ESX-2092658 11:29:03 04/27/07 SNMP agent returns full VM config file.

ESX-2031037 11:38:00 04/27/07 To provide LUN an unique ID Name

ESX-1271657 11:40:02 04/27/07 Open IPMI improvement for slowness.

ESX-6856573 11:53:54 04/27/07 PhysMem_Get() accesses wrong pages

ESX-5885387 11:56:02 04/27/07 RedHat Moderate: gzip security update

ESX-5031800 11:58:11 04/27/07 RHSA-2006:0749 tar security update

ESX-3199476 12:00:22 04/27/07 VMXNET shutdown may lead to BSOD

ESX-9916286 12:02:39 04/27/07 To update zlib library for ESX 3.0.1

ESX-1161870 12:26:30 04/27/07 Several bug fixes in vmware-vmx.

ESX-3416571 12:27:00 04/27/07 Potential Buffer Overflow.

ESX-5011126 12:27:30 04/27/07 Potential Buffer Overflow.

ESX-7737432 12:27:56 04/27/07 Potential Buffer Overflow.

ESX-7780490 12:28:22 04/27/07 Potential Buffer Overflow.

ESX-8174018 12:28:50 04/27/07 Potential Buffer Overflow.

ESX-8852210 12:30:40 04/27/07 Potential Buffer Overflow.

ESX-9617902 12:31:29 04/27/07 Potential Buffer Overflow.

ESX-2559638 12:50:52 04/27/07 Update info rpm for ESX 3.0.1.

ESX-2257739 12:52:47 04/27/07 To deliver several fixes in vmkernel.

For a differential list of rpms, use the -l/--listrpms option.

-


0 Kudos
rex___co
Contributor
Contributor
Jump to solution

Hi Jyothi,

I can reproduce this. Here is a typical output of the 8 patches that failed.

This output is self-explanatory:

-


# cd ESX350-200712403-SG

# ls -la

total 1504

drwxr-xr-x 3 root root 4096 Jan 10 18:37 .

drwxr-xr-x 11 davey davey 4096 Feb 24 10:31 ..

-rw-rr 1 root root 3146 Jan 10 18:37 contents.xml

-rw-rr 1 root root 701 Jan 10 18:37 contents.xml.sig

-rw-rr 1 root root 1390 Jan 10 18:37 descriptor.xml

drwxr-xr-x 2 root root 4096 Jan 10 18:37 headers

-rrr-- 1 root root 37116 Jan 10 18:37 losetup-2.11y-31.24vmw.i386.rpm

-rrr-- 1 root root 114817 Jan 10 18:37 mount-2.11y-31.24vmw.i386.rpm

-rrr-- 1 root root 1343661 Jan 10 18:37 util-linux-2.11y-31.24vmw.i386.rpm

# esxupdate -n update

INFO: No repository URL specified, going with file:///home/davey/updates/3.5_patches/ESX350-200712403-SG

INFO: Configuring...

ERROR: Bundle ESX350-200712403-SG is obsoleted by http://'3.5.0-64607'

# date

Sun Feb 24 22:06:04 PST 2008

# md5sum ESX350-200712402-SG.zip

d83eeef80e27b739546915bc17390ac0 ESX350-200712402-SG.zip

0 Kudos
jyothim
VMware Employee
VMware Employee
Jump to solution

Hi Rex,

Thanks for the update. From the query output, I see that you have ESX-3.0.1 build#32039 and not ESX-3.0.2. The GA build for ESX-3.0.2 is 52542. Well, we have released the re-spin to ESX-3.5 build#64607 on Feb 20th. Please try the same with this release. The one that got released on Feb-16th is only to upgrade from ESX-3.0.2 to ESX-3.5 and is not applicable to ESX-3.0.1, as we have a known upgrade issue. So, please try to use the latest release of ESX-3.5 GA (build#64607) which got released on Feb-20th and then try to upgrade with the ESX-3.5 patches. I really appreciate your quick response:).

Thanks,

Jyothi

0 Kudos
rex___co
Contributor
Contributor
Jump to solution

As you can see below (on the 2nd to the last line), i did use the latest release of the 3.5 GA release (build#64607)

# esxupdate -l query

Installed software bundles:

-


Name -


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

ESX-1006511 11:48:46 04/30/07 Fixing TX hang in 80003ES2LAN Controll er

ESX-9986131 11:57:58 04/30/07 Updated openssh, python, and openssl

ESX-8173580 12:11:06 04/30/07 Fix COS Oops running Dell OM5 w/ QLogi c

ESX-6921838 12:17:33 04/30/07 hot removal of a virtual disk thru SDK

ESX-2066306 12:23:30 04/30/07 Patch for VM crashes and possible free ze

ESX-5497987 12:28:14 04/30/07 Fixes a misleading locking message.

ESX-2092658 12:38:22 04/30/07 SNMP agent returns full VM config file .

ESX-2031037 12:49:37 04/30/07 To provide LUN an unique ID Name

ESX-1271657 12:50:36 04/30/07 Open IPMI improvement for slowness.

ESX-6856573 13:00:35 04/30/07 PhysMem_Get() accesses wrong pages

ESX-5885387 13:01:15 04/30/07 RedHat Moderate: gzip security update

ESX-5031800 13:02:01 04/30/07 RHSA-2006:0749 tar security update

ESX-3199476 13:03:05 04/30/07 VMXNET shutdown may lead to BSOD

ESX-9916286 13:04:19 04/30/07 To update zlib library for ESX 3.0.1

ESX-1161870 13:26:12 04/30/07 Several bug fixes in vmware-vmx.

ESX-3416571 13:26:40 04/30/07 Potential Buffer Overflow.

ESX-5011126 13:27:11 04/30/07 Potential Buffer Overflow.

ESX-7737432 13:27:38 04/30/07 Potential Buffer Overflow.

ESX-7780490 13:28:04 04/30/07 Potential Buffer Overflow.

ESX-8174018 13:28:32 04/30/07 Potential Buffer Overflow.

ESX-8852210 13:30:23 04/30/07 Potential Buffer Overflow.

ESX-9617902 13:31:12 04/30/07 Potential Buffer Overflow.

ESX-2559638 13:49:50 04/30/07 Update info rpm for ESX 3.0.1.

ESX-2257739 13:54:06 04/30/07 To deliver several fixes in vmkernel.

3.5.0-64607 10:42:07 02/24/08 ESX 3.0.x to 3.5.0-77267 upgrade

ESX350-200712402-SG 10:51:54 02/24/08 samba security update

0 Kudos
jyothim
VMware Employee
VMware Employee
Jump to solution

Can you please provide me the /var/log/vmware/esxupdate.log as an attachment, so that I can look into the problem more deeply? Are you part of VMware?

Thanks,

Jyothi

rex___co
Contributor
Contributor
Jump to solution

here ya go.

no, i'm not part of VMWare. I work for a financial company.

0 Kudos
jyothim
VMware Employee
VMware Employee
Jump to solution

Thanks Rex, I really appreciate your feedback. We are looking into the matter. It is certainly not a problem to you as the bundles are getting obsoleted by ESX-3.5.0 GA. I will keep you informed on this, stay online.

-Jyothi

rex___co
Contributor
Contributor
Jump to solution

Are you building a test system in the lab to reproduce my upgrade path?

0 Kudos
jyothim
VMware Employee
VMware Employee
Jump to solution

Rex,

We have already on top of the problem... We could recreate it and are looking into the issue. You can expect the resolution ASAP.

-Jyothi

0 Kudos
rex___co
Contributor
Contributor
Jump to solution

of course ASAP means as soon as possible....can you be a little more specific?

what have you discovered?

Do you have a plan?

What is it?

0 Kudos
rex___co
Contributor
Contributor
Jump to solution

another day has passed.

please respond with your plan and time estimate.

thanks

0 Kudos
rex___co
Contributor
Contributor
Jump to solution

several more days have passed and I have recieved no response from you.

please respond on the status of this issue.

0 Kudos