11 Replies Latest reply on Aug 19, 2019 7:30 AM by Schaedle

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

    rm_bk Lurker

      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!