ESXi

 View Only
  • 1.  Patch conflict issue

    Posted Jan 07, 2010 04:45 PM

    So I was all excited about the release of patch ESX400-200912401-BG only to find out that I can't install it!

    The Vcenter update manager shows that the patch has a conflict with some VEM400 patches, all of which appear to be related to the Cisco Switch, which we don't have.

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

    I tried creating my own baseline, which did not include the VEM patches. No dice.

    Anyone know how I can get this to work?

    Thanks,

    Bob



  • 2.  RE: Patch conflict issue

    Posted Jan 07, 2010 05:46 PM

    Seeing the same issue on both of our vSphere clusters as well.



  • 3.  RE: Patch conflict issue

    Posted Jan 07, 2010 05:52 PM

    I started a case and will update this forum if I get any info.

    Bob



  • 4.  RE: Patch conflict issue

    Posted Jan 08, 2010 04:17 PM

    Getting the same issue in our infrastructure. I hope we get an official answer soon.



  • 5.  RE: Patch conflict issue

    Posted Jan 08, 2010 05:33 PM

    So here is the deal:

    If the baseline attached to the host contains the VEM patches associated with the Cisco switch it will not allow the patch.

    ALSO, if the VCenter Server is on the host your are trying to stage it will fail. (Which is why I couldn't get mine to work.).

    So, in order to get this patch done:

    Create a Baseline which does not include the Cisco patches. Dynamic with VMWare only will work.

    Remove the default "critical host patches" baseline, and any other which may have the Cisco patches.

    Add the custom baseline created above.

    Make sure the VCenter VM is not on the host and patch.

    Hope that helps.

    Bob



  • 6.  RE: Patch conflict issue

    Posted Jan 09, 2010 02:31 AM

    Your solution worked great for me, thanks for posting.

    I did notice an issue in the KB about this, but not this specific patch, from November. It looks to be the same Cisco issue, just a different patch. They should update the KB with this issue and provide your work-around.