Upgrade HP vSphere 5.5 to 5.5 U1 – Error Conflicting VIBS

[ChrisHaag]

We have a small vSphere Environment using the Essentials edition.  We have no Update Manager. To update we (virtually – using iLO) mount the installation .iso, boot from it and choose “upgrade” in the installation process. This process always worked fine – so far.

Attempting to upgrade from HP vSphere 5.5 to HP vSphere 5.5 U1 ends with the following error:

Errors/Warnings during system scan

CONFLICTING_VIBS ERROR […] Remove the conflicting vibs or use Image Builder to create a custom ISO providing newer versions of the conflicting vibs

[Broadcomm_bootbank_net-bnx2_2.2.5dv55-10OEM.550.0.0.1331828]

The current version 5.5 is a HP custom ISO as well as the version 5.5 U1 I tried to upgrade to.

This appears to me very similar to https://communities.vmware.com/thread/482105., which is marked solved although it appears to me it is more a workaround used there.

Any ideas? Do I have to wait for an updated version from HP?

[GustavoAyala]

Just to confirm that the install method of 1.7a over 1.78 worked for me.

Starting from 5.5U1:

/tmp # esxcli software vib install  -d /tmp/BCM-NetXtremeII-4.0-offline_bundle-1796156.zip

Installation Result

   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

   Reboot Required: true

   VIBs Installed: Broadcom_bootbank_misc-cnic-register_1.7a.02.v55.1-1OEM.550.0.0.1331820, Broadcom_bootbank_net-bnx2_2.2.5d.v55.2-1OEM.550.0.0.1331820, Broadcom_bootbank_net-bnx2x_1.7a.10.v55.1-1OEM.550.0.0.1331820, Broadcom_bootbank_net-cnic_1.7a.05.v55.3-1OEM.550.0.0.1331820, Broadcom_bootbank_scsi-bnx2fc_1.7a.08.v55.1-1OEM.550.0.0.1331820, Broadcom_bootbank_scsi-bnx2i_2.7a.03.v55.2-1OEM.550.0.0.1331820

   VIBs Removed  : Broadcom_bootbank_misc-cnic-register_1.78.75.v55.1-1OEM.550.0.0.1331820, Broadcom_bootbank_net-bnx2_2.2.4f.v55.3-1OEM.550.0.0.1331820, Broadcom_bootbank_net-bnx2x_1.78.80.v55.3-1OEM.550.0.0.1331820, Broadcom_bootbank_net-cnic_1.78.76.v55.7-1OEM.550.0.0.1331820, Broadcom_bootbank_scsi-bnx2fc_1.78.76.v55.1-1OEM.550.0.0.1331820, Broadcom_bootbank_scsi-bnx2i_2.78.76.v55.1-1OEM.550.0.0.1331820

   VIBs Skipped:

Then everything goes smoothly to 5.5U1A

[vlho]

Hi,

here:

VMware KB: Upgrading a host using HP Custom Image VMware ESXi 5.5 Update 1 fails with conflicting vi...

is official statement (resolution) from VMware...

[Fluckinger]

Hi,

we had the same problems updating 2 DL380p Gen8 and 1 DL380 G7 from ESXi 5.0 to 5.5.0 Update 1 (June)

I followed ddssupports steps, and it worked like a charm! Thank you!

The iLO Remote Console (e.g. Mount Image to CD/DVD Drive) is a perfect tool for upgrading servers from at home 🙂

[mikefsc]

I have the same problem with a DL380 G7 upgrading from 5.0U2 to 5.5U1 using the HP 5.5U1 June 1014 custom image.

I followed ddssupports steps that others have followed above and the upgrade was then successful.  I have created a case with HP support.  They are allowing me to download the March 2014 image from their FTP site.

[mikefsc]

Just heard back from HP and I quote.

"at this time the expected release date of an updated image will be in September."

[caseylcc]

do you have a link to the March 2014 image iso please?

[sp4rt4n]

I've uploaded the ISO to my Google Drive, but unfortunately cannot provide the checksums, so it's your decision to download or not:

https://drive.google.com/file/d/0B06zPdui-TqcVUIyUHFBRWk5N28/edit?usp=sharing

edit: I meant the original VMWare-checksums! (maybe someone else could provide it)

The checksums of my ISO are the following:

MD5: 7a03083e5d04803fae40eb6fbe0386c6

SHA1: 2da6dcee563504e51aa8cf4ac1f115810b5232c9

[vNEX]

Hello Chris,

it seems to be a known issue but with just workarounds see:

VMware KB:     Upgrading a host using HP Custom Image VMware ESXi 5.5 Update 1 fails with conflictin...

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 at VMware Downloads. Use this modified image to upgrade the hosts.
  
  Note: Using a custom image does not prevent you from using the HP image at a later date.

Here is another approach which solved this issue:

Upgrade ESXi 5.5 to ESXi 5.5 U1 using HP image fails | VCDX56

For HP supplied images go to:

http://h18004.www1.hp.com/products/servers/software/vmware-esxi/driver_version.html

_________________________________________________________________________________________

If you found this or any other answer helpful, please consider to award points. (use Helpful or Correct buttons)

Regards,

P.

[xinghai8]

-Solved the issue, better than what's explained in VMware KB

-My only issue is this patch bundle can't be pushed via VUM.

[Mackopes]

This Patch bundle is the updated driver bundle that can be imported into VUM:

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

[xinghai8]

Thanks for the note. After the host upgrade, I believe the patch download will pick it up as well? I will test it.

[MoreCore]

Update 2 is now available for download.  Applied the update via Update Manager and it worked.  This would be the first I have ever used Update Manager and I noticed that even though the hosts have been updated, it shows up as not compliant.  I did do a rescan with the Update 2 baseline that was applied.

Please advise.

Thanks

[VRBitman]

Manually check if the hosts are up-to-date. Sometimes VUM will report success after remediating one or more hosts when in reality the operation fails. One possible cause is that there is insufficient free space under /tmp.

[MoreCore]

~ # vmware -v

VMware ESXi 5.5.0 build-2068190

Looks good to me.

How does one check the free space under /tmp?

Thanks

[VRBitman]

Try:

vdf -h

It was just a suggestion though, the build number is indeed correct and it may have actually completed successfully. This would mean the problem lies somewhere else.. but check the free space just to be sure.

[MoreCore]

Ramdisk	Size	Used Available Use% Mounted on
root	32M	2M	29M   6% --
etc	28M	320K	27M   1% --
tmp	192M	8K	191M   0% --
hostdstats	553M	6M	546M   1% --

Hmmm, this appears to be good too.  Would be interesting to hear if others notice the same thing before I open a ticket.

Thanks!

[SatyS]

This is a known issue.

Please see the KB:VMware KB: Upgrading a host using HP Custom Image VMware ESXi 5.5 Update 1 fails with conflicting vi...

As said in KB:

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 at VMware Downloads. Use this modified image to upgrade the hosts,

Hope this helps !!!

[MoreCore]

Thanks SatyS but that is not the issue I'm having.  Please re-read my Post 31.

I have opened a ticket with vmware support on the persistent non-compliance after updating with U2. 

[mikefsc]

The Update 2 Sept 2014 HP custom image is available on the HP download site. 

[krainbolt]

Did you hear back from vmware support?

I am having the exact same problem.  Using VUM to upgrade from HP ESXi 5.5 U1 to HP ESXi 5.5 U2 image seems to complete successfully and I've ran the tests listed above.  All tests look good - exactly as your situation.  VMware Update Manager still reports "non-compliant" for the upgrade.