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,
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)
.
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
root@server tmp# 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
root@server tmp#
here's the dump from the esxupdate.log
Expanding Vibs for bulletin ESX400-200912401-BG
[2010-03-16
00:39:39|http://communities.vmware.com/community-document-picker.jspa?communityID=&subject=2010-03-16+00%3A39%3A39] DEBUG: cmdline: Applicable=5 Conflicting=0
Installed=21 Obsolete=1
[2010-03-16
00:39:39|http://communities.vmware.com/community-document-picker.jspa?communityID=&subject=2010-03-16+00%3A39%3A39] DEBUG: cmdline: Vibs from bulletins: set(--rpm_vmware-esx-perftools_4.0.0-1.10.219382@i386:uninstalled,
rpm_vmware-esx-vmkernel64_4.0.0-1.10.219382@i386:uninstalled,
rpm_dhcp-cos_4.0.0-1.1625.vmw2@i686:uninstalled,
rpm_nspr_4.7.6-1.2213.vmw@x86_64:uninstalled,
rpm_vmware-esx-cim_4.0.0-1.10.219382@i386:uninstalled,
rpm_nss_3.12.3.99.3-1.2157.vmw@x86_64:uninstalled,
rpm_vmware-esx-tools_4.0.0-1.10.219382@i386:uninstalled,
rpm_vmware-esx-drivers-vmklinux-vmklinux_4.0.0-1.10.219382@x86_64:uninstalled,
rpm_openssl097a_0.9.7a-9.el5_2.1@x86_64:uninstalled,
rpm_openssl097a_0.9.7a-9.el5_2.1@i386:uninstalled--)
[2010-03-16
00:39:39|http://communities.vmware.com/community-document-picker.jspa?communityID=&subject=2010-03-16+00%3A39%3A39] 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, many thanks for any suggestions.....
What about this situation: http://communities.vmware.com/thread/249759
It seems that it's a known error one can run into while update.
---
iSCSI SAN software
http://www.starwindsoftware.com
Paul,
Thanks for the reply - unfortunately I tried the suggestion in the link:
esxupdate query --vib-view
but couldn't find anything mentioning Cisco in it, and I'm actually on 4.0 U1 already so just applying a patch but it doesn't want to install for some reason.
Many thanks,
Hi,
Please follow the below steps,
1. Download https://hostupdate.vmware.com/software/VUM/OFFLINE/release-181-20091231-153046/ESX400-200912001.zip and copy to the server
2. run esxupdate --bundle ESX400-200912001.zip scan
3. Make sure that bulletin named ESX400-200912401-BG is listing
4. Run esxupdate --bundle ESX400-200912001.zip -b ESX400-200912401-BG stage
5. Once the staging completed successfully, run esxupdate --bundle ESX400-200912001.zip -b ESX400-200912401-BG update.
Before doing the above operation, we would like to look in to the logs and some of the details. Please collect esxupdate.log, esxupdate -a query, esxupdate --vib-view query , rpm -qa , vnware -v, vmware -l and upload it.
Thanks
I have the same with three updates:
ESX400-200912401-BG
ESX400-201002401-BG
ESX400-201003401-BG
Should I install all manualy on all ESX? It must be another way.
Actually for me after I placed a call with VMware the engineer told me was my installation of vSphere already had that component covered in the release of vSphjere I installed and asked me to exclude it from the vCentre Update Manager.