VMware Cloud Community
DCurrie
Contributor
Contributor
Jump to solution

Using Update Manager to upgrade ESX 5.1 to 5.5 - ERROR Conflicting VIBS


Hi

I hope somebody can help. I have a number of 5.1 ESX hosts which I would like to upgrade to 5.5 using Update Manager which seems straight forward enough....... right

vCentre is at 5.5

Import the ESXi ISO to Update Manager

Create a Baseline

Attach Baseline to the host to be upgraded

Scan and Remediate

.... Simple

The problem I am having is that we use the HP Custom image as they are all HP servers, makes sense, right. I have downloaded the HP 5.5 Custom Image ISO from the VMWare site and imported the ISO to Update Manager, created a baseline, attached it to a test host ( DL585 G5 ) and run a scan. Im then presented with an incompatible warning and the details show the below

Conflicting VIBS error.JPG

I have been searching the net for a solution and found multiple entries about dealing with conflicting VIBs and creating custom ISOs, which I have also downloaded the HP ESX Depot ZIP file and created a custom ISO which does not work either.

Below is the current Broadcom VIBs installed on my ESX test host

Broadcom drivers Installed.JPG

I also cant remove the conflicting VIBs as they are the network card drivers and if I do remove them and reboot the host has not network adapters ( yup, i tried that ).

Its been 2 days of pulling my hair out :smileyangry: and maybe I am missing something simple.

Anybody have any ideas ?

:smileyconfused:

Thanks

36 Replies
roeschuxxx
Contributor
Contributor
Jump to solution

Ahhh...same issue..

From the workarounds:

************

This is a known issue with ESXi 5.5 Update 1.


Currently, there is no resolution.

To work around this issue, use one of these methods:

  • Contact HP support and request an updated HP Custom Image for ESXi 5.5 Update 1.
  • Upgrade the host using the HP 5.5 Update 1 March 2014 image and then apply latest patches.
  • Build a custom ISO with HP 5.5 Update 1 June 2014. Remove the Broadcom NX2 packages and replace with the older version from the HP 5.5 GA build available here. Use this modified image to upgrade the hosts.

***************

Did anyone tried to upgrade via VUM from 5.1 to 5.5u1 with the March 2014 HP Image? I would like to try that...but cant find the March 2014 on the HP page Customize VMware ESXi Images for HP ProLiant Servers...grrr

Reply
0 Kudos
KildairService
Contributor
Contributor
Jump to solution

Thank you very much this solved our problem here on our HP Proliant dl380p Gen8.

Updating wasn't working at first:


FROM: VMware-ESXi-5.5.0-1331820-HP-5.71.3-Sep2013.iso (ESXI 5.5 Build 1331820)

TO: VMware-ESXi-5.5.0-Update1-1746018-HP-5.74.27-Jun2014.iso (ESXI 5.5U1 Build 1746018)

Manually updating the Broadcom drivers corrected the issue using the 5.5U1 update ISO on a USB key !

Thanks

Reply
0 Kudos
bob_osborne
Contributor
Contributor
Jump to solution

I contacted HP last night, and after a significant run-around was forwarded a private link to download the March ISO. Unfortunately, Update Manager (which I intend to use) immediately flags it as non-compliant. I've updated the HP case with this info, but have yet to hear anything back. They seemed quite surprised by the issue, even after being pointed to this thread and the associated KB article.

guessing this isn't the response that you wanted, but hate to see anyone else go through the HP support pains I did to receive a file that doesn't work.

Reply
0 Kudos
kwohlgemuth
Contributor
Contributor
Jump to solution

bpjones, good to know about the ESXi-Customizer. Was hoping that it might have made things a bit easier.

Reply
0 Kudos
LasseH
Contributor
Contributor
Jump to solution

I have same issue upgrading from 5.1 to 5.5 U1 using HP Custom ISO. And there's nothing new in VMware KB since 25th of july.

I'll check in a few days and hope for good news, coz what's the point in using the 5.5GA from HP, when you have to upgrade further to U1. Come on, you can do it Smiley Happy

Reply
0 Kudos
wkraai
Contributor
Contributor
Jump to solution

Hi

I've ran into the same problem upgrading 5.1u2 to 5.5u1.

Problem was the broadcom driver. Building a new image was one option and deploy using Update Manager. Or install other broadcom drivers.

BCM-NetXtremeII-12.0-offline_bundle-1821661.zip was the solution in my case.

Reply
0 Kudos
damo_s
Contributor
Contributor
Jump to solution

Hi All,

Thanks for your input on this, I had exactly the same issue upgrading from 5.1U2 to 5.5U1:

Custom ISO, altering drivers and such sounded plausible but thought I'd try the easier option first and it worked; I downloaded the March release of the HP ESXi 5.5U1 image that was removed from general release and replaced with the June/July release as the March one had the Heartbleed vulnerability.

I installed the March release via update manager, applied all updates after reboot, now I'm up to speed and on a newer build than the ISO that was giving me the errors to start with.

Found the March release here: http://ddl1.digiboy.ir/vmware/5.5/VMware-ESXi-5.5.0-Update1-1623387-HP-5.73.17-Mar2014.iso

Not my site but the MD5 checksums check out and it has worked fine for me!

Reply
0 Kudos
damo_s
Contributor
Contributor
Jump to solution

NOTE!!!

This worked fine on the first 4 hosts I did, the last two got stuck on the purple screen of death.

The difference was I installed all available patched (option and critical) before doing the upgrade, I did not do this on the last two and they both failed. So may be an idea to make sure all your patches are up to date too.

Reply
0 Kudos
sp4rt4n
Enthusiast
Enthusiast
Jump to solution

damo_s schrieb:

Hi All,

Thanks for your input on this, I had exactly the same issue upgrading from 5.1U2 to 5.5U1:

Custom ISO, altering drivers and such sounded plausible but thought I'd try the easier option first and it worked; I downloaded the March release of the HP ESXi 5.5U1 image that was removed from general release and replaced with the June/July release as the March one had the Heartbleed vulnerability.

I installed the March release via update manager, applied all updates after reboot, now I'm up to speed and on a newer build than the ISO that was giving me the errors to start with.

Found the March release here: http://ddl1.digiboy.ir/vmware/5.5/VMware-ESXi-5.5.0-Update1-1623387-HP-5.73.17-Mar2014.iso

Not my site but the MD5 checksums check out and it has worked fine for me!

Please note that it isn't the best idea to use an ISO, which was shortly replaced by HP due to an issue documented here and here

You should rather use the newer March ISO (VMware-ESXi-5.5.0-Update1-1623387-HP-5.73.21-Mar2014.iso), if available. Otherwise checkout my post in the other thread.

Reply
0 Kudos
LasseH
Contributor
Contributor
Jump to solution

Follow up on my last post.

I did the same workarround a few days after I posted this (just couldn't wait) Smiley Happy

1. Upgrade of my 5 esxi 5.1 hosts to newest patch.

2. Downloaded the esxi image (VMware-ESXI-5.5.0-1746974-HP-5.72A.3-Jun2014.iso) from VMware download.

3. Uploaded the esxi image in vCenter and created baseline in Update Manager.

4. Scan all hosts (Cluster), so status is non-compliant instead of Incompatible.

5. Put the host in Maintenance mode.

6. Remediated host with the attached baseline for esxi image (had a ILO console to the host while upgrading, because when upgrade is finished you'll have to press ENTER to confirm the last reboot)

7. When host is up and available in vCenter, then scan for new patches.

8. 20 updates (for esxi 5.5) were found and remediated them.

My environment is now up and running the latest version (VMware ESXi, 5.5.0, 1892794), hope I save you guys some time.

Reply
0 Kudos
Mackopes
Enthusiast
Enthusiast
Jump to solution

FYI, I was able to successfully use bpjones process to create a custom ISO. In addition, instead of using an 'older' BCM-NetXtremeII-3.0-offline_bundle-1566459.zip Nic driver, looks like Broadcom as released an updated one a few days ago which is the 1.7a.x driver with the only fix to change the driver version to 1.710.x (which will work with VUM).  BCM-NetXtremeII-5.0-offline_bundle-1962044.zip


I tested this successfully on a BL460c G6 & BL460c G7 to upgrade from esxi 5.0U3 --> 5.5U1 and I also imported the driver directly into VUM and was able to update a 'march-iso-upgraded' host (gen8) successfully.


Here's the Download and a snippet release notes.

https://my.vmware.com/web/vmware/details?productId=351&downloadGroup=DT-ESXI55-QLOGIC-BNX2X-171010V5...

Version 1.710.10.v[50,55].1 (Jun 24, 2014)

====================================

Internal FW 7.10.7

Fixes:

------

   1.  Problem: (VMware PRs 1268606 and 1273517) VIB update failing due to

                driver version.

       Cause:  The driver was using string 7a in the driver version. The VMware

               update manager considers this string as lower than the versions

               used in previous async/inbox drivers and hence update fails.

       Change: Changed string 7a in driver version to 710 to allow update from

               previous async/inbox drivers.

       Impact: Package update.

Reply
0 Kudos
jslarouche
Enthusiast
Enthusiast
Jump to solution

Hi all,

I ran into this issue earlier today using the following file - VMware-ESXi-5.5.0-Update1-1746018-HP-5.74.27-Jun2014.iso on a 5.0 U3 host while using VUM.

I rolled back to the following file VMware-ESXi-5.5.0-Update1-1623387-HP-5.73.21-Mar2014.iso and got passed the vibs error and was able to complete the in-place upgrade to ESXi 5.5.

Reply
0 Kudos
MarcSmid
Contributor
Contributor
Jump to solution

Does anyone know if this issue is resolved with the sept issue of the ISO ?

Reply
0 Kudos
mitsumaui
Contributor
Contributor
Jump to solution

HP say it is, however not tested yet. Please post back if you manage to test before we do!

Reply
0 Kudos
OlivierLL
Contributor
Contributor
Jump to solution

Hello All,

It worked for me ! I had the same initial issue (conflicting VIBs) on a DL180 G6 but I am just using the standard update through ISO booting, not through VUM.

Here is what happened to me :

- I needed to ugrade from 5.1 to 5.5, so I tried to do it in June using the 5.5 Update 1 and faced the conflicting VIBs issue documented above.

- I upgraded then to 5.5 initial release successfully, tried to apply 5.5U1 on top of it and it did not work either for the same issue.

- I applied today the 5.5U2 and everything went fine.

Reply
0 Kudos
TedBWork
Contributor
Contributor
Jump to solution

SAME HERE!

5.5U2 worked correctly.  Looks like they have addressed the the VIB issue here!

Reply
0 Kudos
SGreffard
Contributor
Contributor
Jump to solution

Hi Friends,

I executed the procedure to solve the issue in the server but. the Build number doesn`t change the build number.

Do you know something to fix this ?

Thanks,

Sandro

Reply
0 Kudos