Patch Sequence?

[crescendas]

Hi,

Our Update Manager is not able to stage or download all the critical patches required for our ESX servers. Thus, we need to manually download and install them. However, there are quite a number of patches available and I like to check does the latest patch contain all the previous patches as well? If not, is it a must to install these patches in sequence according to their release date?

Thanks,

Boon Hong.

[rogard]

I would be more tempted to troubleshoot the connectivity with vcenter.

[AndreTheGiant]

On VMware site you will see if a patch will contain other patches.

But check why stagin does not work, cause seems strange. Do you have enough free space in your COS filesystem?

Andre

[depping]

Patches don't contain previous patches in general. Updates do contain all patches up to that date and basically bring you up to the latest level.

Duncan

VMware Communities User Moderator | VCDX

-

---

Now available: <a href="http://www.amazon.com/gp/product/1439263450?ie=UTF8&tag=yellowbricks-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=1439263450">Paper - vSphere 4.0 Quick Start Guide (via amazon.com)</a> | <a href="http://www.lulu.com/product/download/vsphere-40-quick-start-guide/6169778">PDF (via lulu.com)</a>

Blogging: http://www.yellow-bricks.com | Twitter: http://www.twitter.com/DuncanYB

[crescendas]

Hi Andre,

We have sufficient storage. The Update Manager show 8 conflicts among the 68 patches that I have staged. Unfortunately the patch that I really want to apply to fix our iSCSI issue is under the conflict section and I was prevented from applying this patch: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101949...

If I am to manually apply this iSCSI patch, does this mean that all the other patches should not be applied since this patch is in conflict with other patches? What is the worst thing that could happen if I applied conflicting patches?

btw, how is it possible that vmware release conflicting patches in the first place?

[Saju_C]

The conflicting status will be shown if you have any CISCO patches installed in your server. ? else, have you downloaded any CISCO patches and are they available in the patch repositoy ?

Thanks

CS

[crescendas]

We don't have any CISCO equipment nor patches installed. I have unselect CISCO patches but the staging still fail.

[Saju_C]

is it possible to attach the error or the screen shot?

[crescendas]

The error message is as followed: (and attached screenshot of the conflicts)

Stage Entity

192.168.190.200

VMware vCenter Update

Manager had an unknown

failure. Check Tasks and

Events tab and logs for more

details.

bhwong

VMTEMPLATE

25-May-10 10:25:14 AM

25-May-10 10:25:14 AM

25-May-10 10:26:18 AM

[Saju_C]

Your patch repository shows Cisco patches and that should be the reason for conflict. Please refer KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101306...

Thanks

Saju

[crescendas]

As mentioned, I have de-selected CISCO patches and the conflict is still here. Moreover, the conflict patches are not CISCO patches, but important iSCSI bugs I want to patch. Staging failed to download these conflicting patches as well.

[Saju_C]

conflict will show even if you select or de-select cisco patches. If cisco patches are in your update manager repository, this conflict is expected ( as per the KB). Update manger conflict checking is with respect to the update manager repository. I understand if you proceed with remediation, the remediation should succeed.

[crescendas]

But there is no point to proceed with remediation when the bugs I want to patch is not downloaded during staging as these are marked as conflict.