VMware Cloud Community
rm_bk
Enthusiast
Enthusiast

ELX_bootbank_elx-esx-libelxima.so conflict between patch baseline and HP custom ISO.

In esxupdate.log when checking compliance in VUM:

ValueError: VIBs ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 and ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 have unequal values of the 'payloads' attribute: '[elx-esx-libelxi: 1602.936 KB]' != '[elx-esx-libelxi: 1493.833 KB]

This is from a host that was installed with the 6.7U2 HPE Custom ISO then patched with the "critical" VUM baseline.  It seems the baseline installs a conflicting vib which breaks VUM compliance checks from that point forward.

If I remove the vib with esxcli software vib remove -n elx-esx-libelxima.so, it allows VUM compliance scanning to resume but then the host reports as non-compliant against the critical patch baseline.

Is there a definitive fix for this?  Can I somehow blacklist this vib within VUM?  We don't even need it -- we don't have this hardware!

24 Replies
DimVKir
Contributor
Contributor

I don't know. There are no new updates to check this now. But, given that the problem was in previous updates (hpe-driver-bundle-670.10.3.0, hpe-driver-bundle-670.10.3.5), there is hope that in the future everything will be fine.

Reply
0 Kudos
DimVKir
Contributor
Contributor

Just installed new updates (from 05.12.2019) - the installation process was successful. There were no problems.

Reply
0 Kudos
rm_bk
Enthusiast
Enthusiast

OP here.  Added the base HPE vibsdepot URL to VUM yesterday and had no issues.  Today I've added the "-drv" variant and brought back all of the libelxima-breaking-host-scan-HPE-driver-bundle-never-installs happy joy described in the two pages above.  Once again I had to uncancer my VUM with a database reset to get it working again.

You ever get the feeling some people just stopped trying?

Reply
0 Kudos
rm_bk
Enthusiast
Enthusiast

So we had to stop using the built-in patch baselines for a reason totally unrelated to this.  Given that we're now on custom baselines and that we have different baselines for different host types, I've decided to take another shot at this.  I now have an 6.7 HPE Gen9 host successfully patched by VUM with both HPE vibsdepot URLs (drivers and value-adds) added to the patch sources.

I don't know which of these actually fixes the issue but here's what's working for me:

  1. PowerCLI or esxcli to remove both elx-esx-libelxima.so and elx-esx-libelxima-8169922.so from the host.  Reboot.
  2. Custom patch baseline with the following patches de-selected:
    1. All occurrences of Device Drivers for HPE ESXi 6.7.0 v670.10.x.x except for the latest.
    2. All occurrences of ESXi 6.7.0 Management Bundle 3.x.x-x except for the latest.
    3. All occurrences of Updates elx-esx-libelxima.so VIB.
    4. All occurrences of Utility Bundle for ESXi 6.7 except the latest.
    5. All occurrences of VMware ESXi 6.7 Complete Update.  I have uploaded an HPE custom image profile to use instead.

I'll speculate that 2 and 4 are innocent in this regard but I've listed them here for completeness.  Step 1 might be a showstopper if you actually need this driver.  We do not.

The PowerCLI was simple:

$esxcli = Get-EsxCli -V2 -VMHost <your host name here>

$esxcli.software.vib.remove.Invoke(@{"vibname" = "<your vib name here>"})    ----- and so on.

---

Edit: After all this was complete, the host wound up with these package versions installed:

elx-esx-libelxima-8169922.so
Emulex OneConnect IMA-Plugin

12.0.1188.0-03

ELX

VMware-certified

elx-esx-libelxima.so
This package contains the IMA plugin of the elxiscsi driver.

11.4.1184.2-3.89.15160138

VMware

VMware-certified

Reply
0 Kudos
augiemoto
Contributor
Contributor

Hi

just wanted to give a thanks for the steps posted to resolve this issue.

i went round and round with HP and they pointed me to this article.

one thing I has issues with was ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03_670.vib

I downloaded this VIB and kept getting an error when installing it on the host "esxupdate: ERROR: vmware.esximage.Errors.DependencyError: VIB VMW_bootbank_net-bnx2_2.2.4f.v60.10-2vmw.650.0.0.4564106 requires com.broadcom.cnic_register-9.2.3.0, but the requirement cannot be satisfied within the ImageProfile"

I rebuilt the host and tried the steps over and over with this same error so I finally downloaded this VIB again and followed the steps and was able to remediate 3 host not sure what happened to the VIB but it was a different size of the original download.

i went back and tried to install this VIB on the original problematic host and got the com.broadcom.cnic error

so I rebuilt it again and it worked, I guess all the removing and adding of the ELX broke something on it.

hope this helps someone out

thanks

Reply
0 Kudos