Re: vCentre 4.0 U1 Update Manager cannot remediate

zenomorph · ‎03-13-2010

Hi,

I've just completed the setup of our first vSphere infrastructure and configured servers Clusters for HA, DRS and vMotion. Now I'm testing the Update Manager.

The baseline and baseline groups have been configured and I've setup 3 baselines

- vSphere Security patch

-vSphere General patch

-vSphere Critical

now I've assigned the Baseline Groups to the host and run a scan and it detects there's missing patches. So I select "remediate" but it seems to get stuck at 16% and cannot finish.

I've already enabled the Firewall rule on vSphere for "vCentre Update Manage - Outgoing". So I'm not sure why its not working.

Can anyone give me some advice please? I've attached the Update Manger Log for reference.

EVW · ‎03-14-2010

I see many messages with conflicting dependencies, but I am not sure if this prevents Update Manager from installing the patches. Here's an example:

Bulletin: VEM400-200904001-BG vib: cross_cisco-vem-v100-esx_4.0.4.1.1.27-0.4.2 conflicts with following vibs installed on the host: vmware-esx-vmkernel64_4.0.0-1.9.208167@i386,

Patch cross_cisco-vem-v100-esx_4.0.4.1.1.27-0.4.2 conflicts with host installed package vmware-esx-vmkernel64_4.0.0-1.9.208167@i386, however, no obsoleting patch can be found in update manager patch repository that can resolve this conflict.

You may try to make a new baseline with lesser options (like only critical updates). Can you manually install one or more patches from the command line ? (http://communities.vmware.com/blogs/vmroyale/2009/10/12/single-use-esxupdate-how-to-for-esx-4)

zenomorph · ‎03-15-2010

EVW,

h6. Actually found the cause of the issue - as suggested I reduced the number of patches and they installed Update Manager worked.

However I found one patch that was causing the issue "Patch ESX400-200912401-BG" it keeps on saying there's a conflict but I cannot identify what the conflict is,

The selected Update conflicts with following Updates in VMware vCenter Update Manager patch repository:

VEM400-200904001-BG, VEM400-200906002-BG, VEM400-200907001-BG, VEM400-200909001-BG, VEM400-200911014-BG, VEM400-201002001-BG, VEM400-201002011-BG.

These patch repository conflicts will NOT affect stage and remediation unless the conflicting Updates are contained in the baseline(s) .

However the problem is I'm not updating any VEM and I'm not running Cisco Nexus either.

I also tried manually installing the patch by copying to the vSphere and running

- esxupdate --bundle "package" info which wen ok.

Then tried to stage it

-esxupdate --bundle ESX400-200912401-BG.zip stage

and I got this error

# esxupdate --bundle ESX400-200912001.zip stage

ESX400-200912001.zip ########################################

The following problems were encountered trying to resolve dependencies:

cross_emulex-cim-provider_400.2.0.27.1-164009 provides 'emulex-cim-provider >= 400.2.0.27.1' (required by rpm_vmware-esx-cim_4.0.0-1.10.219382@i386), but is obsoleted by the host

#

here's the dump from the esxupdate.log

Expanding Vibs for bulletin ESX400-200912401-BG

DEBUG: cmdline: Applicable=5 Conflicting=0 Installed=21 Obsolete=1

DEBUG: cmdline: Vibs from bulletins: set()

ERROR: esxupdate: An esxupdate error exception was caught:

Traceback (most recent call last):

File "/usr/sbin/esxupdate", line 242, in ?

cmd.Run()

File "/usr/lib/vmware/python2.4/site-packages/vmware/esx4update/cmdline.py", line 357, in Run

deps = solver.Resolve()

File "/usr/lib/vmware/python2.4/site-packages/vmware/esx4update/depsolver.py", line 453, in Resolve

raise errors.DependencyError(problems)

DependencyError: cross_emulex-cim-provider_400.2.0.27.1-164009 provides 'emulex-cim-provider >= 400.2.0.27.1' (required by rpm_vmware-esx-cim_4.0.0-1.10.219382@i386), but is obsoleted by the host

My vSphere is version 4.0 U1.

WarrenEsterman1 · ‎02-04-2012

Hello All

I am running Vcentre 4.1 Update 2 on windows 2008 X62 SP2. I am tying to remediate an ESX host in my estate - ESX 4.1.0 381591 using Update manager. I would like to deploy the 29 patches including 'ESX 4.1 complete update 2' which is available within my repository for deployment. I have successfully deployed all the patches to an ESX 4.1.0 433742 host without any conflicts or issues. It is only to the ESX 4.1.0 381591 hosts I am having the conflicts.

Below is the errors I get:

Host patch ESX410-201110201-SG conflicts with the package pam_per_user
-0.4-505.vmw@i686 installed on the host and cannot be remediated.
Remove the patch from the baseline or include any suggested additional
patches in the baseline and retry remediation operation.
error
Remediate entity

Host patch ESX410-201112401-BG conflicts with the package pam_per_user
-0.4-505.vmw@i686 installed on the host and cannot be remediated.
Remove the patch from the baseline or include any suggested additional
patches in the baseline and retry remediation operation.
error
Remediate entity

Host patch ESX410-201201401-SG conflicts with the package pam_per_user
-0.4-505.vmw@i686 installed on the host and cannot be remediated.
Remove the patch from the baseline or include any suggested additional
patches in the baseline and retry remediation operation.
error
Remediate entity

Host patch ESX410-Update02 conflicts with the package pam_per_user-0.4-
505.vmw@i686 installed on the host and cannot be remediated. Remove
the patch from the baseline or include any suggested additional patches in
the baseline and retry remediation operation.
error
Remediate entity

Host patch ESX410-201107401-BG conflicts with the package pam_per_user
-0.4-505.vmw@i686 installed on the host and cannot be remediated.
Remove the patch from the baseline or include any suggested additional
patches in the baseline and retry remediation operation.
error
Remediate entity

It seems to be the same package currently on the ESX host causing the conflict - pam_per_user
-0.4-505.vmw@i686.

What is this and is there any way to remove this package so this ESX host can accept the same list of patches as the ESX 4.1.0 433742 host?

Any help or advice would be much appreciated

Thanks

Warren

vmwaredownload · ‎02-04-2012

I had a similar issue previously. I fixed it by removing uninstalling Update Manager software and reinstalling. When resinstalling just select the option to scrap the old DB and use a fresh one. It seems the DB had become corrupt and I didnt want to waste time digging through the logs to determine why when it was a quick and easy fix.

Be aware. This will destroy your baselines and such and any customizations you have made to VUM will be lsot as well. Though, VUM is pretty straight forward.