vmware upgrade 6.5 alerted for removal of VIBS 2

I had ran this command:
esxcli software profile install -p ESXi-6.5.0-20171004001-standard -d https://hostupdate.vmware.com/software/VUM/PRODU
to upgrade to the latest version of 6.5 vmware ESXi and I got this message:

[Exception]
You attempted to install an image profile which would have resulted in the removal of VIBs [‘HPE_bootbank_hpe-cru_650.6.5.8.24-1.4240417’, ‘HPE_bootbank_hponcfg_6.0.0.4.4-2.4.2494585’, ‘HPE_bootbank_scsi-hpvsa_5.5.0.102-1OEM.550.0.0.1331820’, ‘HPE_bootbank_hpe-esxi-fc-enablement_650.2.6.10-4240417’, ‘HPE_bootbank_hptestevent_6.0.0.01-01.00.5.2494585’, ‘HPE_bootbank_hpe-ilo_650.10.0.1-24.4240417’, ‘HPE_bootbank_ssacli_2.65.7.0-6.5.0.4240417’, ‘HPE_bootbank_hpbootcfg_6.0.0.02-02.00.6.2494585’, ‘HPE_bootbank_hpe-smx-provider_650.03.11.00.17-4240417’, ‘HPE_bootbank_amshelper_650.10.6.0-24.4240417’, ‘HPE_bootbank_conrep_6.0.0.01-02.00.1.2494585’]. If this is not what you intended, you may use the esxcli software profile update command to preserve the VIBs above. If this is what you intended, please use the –ok-to-remove option to explicitly allow the removal.
Please refer to the log file for more details.

I wanted to keep those VIBs because I know there were no upgrades for HP on them, so I ran an update command instead:

esxcli software profile install -p ESXi-6.5.0-20171004001-standard -d https://hostupdate.vmware.com/software/VUM/PRODU

Facebooktwitterredditpinterestlinkedinmail

2 thoughts on “vmware upgrade 6.5 alerted for removal of VIBS

  1. Reply Harry P. Nyce Aug 26,2019 5:40 pm

    What’d you ever do to work around/through this? I don’t really recall what I did previously, beyond just waiting for the custom images from HPE and Cisco to land on the official VMware site. Today I’m experiencing the same/similar issues trying to upgrade from 6.7.0 Update 2 (Build 13644319) on my Cisco box and 6.7.0 Update 2 (Build 13981272) on the HPE. esxcli.log shows the following (for both systems):

    [2019-08-26 21:32:31,404 root ERROR] install failed: [ProfileVibRemoval]
    You attempted to install an image profile which would have resulted in the removal of VIBs {'MEL_bootbank_nmst_4.9.0.38-1OEM.650.0.0.4598673', 'HPE_bootbank_conrep_6.7.0.03-02.00.1.7535516', 'QLC_bootbank_qedrntv_3.9.18.0-1OEM.670.0.0.7535516', 'Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.60-1OEM.550.0.0.1331820', 'HPE_bootbank_ilo_670.10.1.0.16-1OEM.670.0.0.7535516', 'HPE_bootbank_oem-build_670.U1.10.3.5-7535516', 'HPE_bootbank_amsd_670.11.3.5-6.7535516', 'HPE_bootbank_bootcfg_6.7.0.02-05.00.4.7535516', 'HPE_bootbank_ssacli_3.30.14.0-6.7.0.7535516', 'HPE_bootbank_testevent_6.7.0.02-00.01.12.7535516', 'HPE_bootbank_hponcfg_6.7.0.5.3-0.2.7535516', 'HPE_bootbank_fc-enablement_670.3.20.12-7535516', 'HPE_bootbank_smx-provider_670.03.14.00.2-7535516', 'HPE_bootbank_cru_670.6.7.10.14-1OEM.670.0.0.7535516'}. If this is not what you intended, you may use the esxcli software profile update command to preserve the VIBs above. If this is what you intended, please use the --ok-to-remove option to explicitly allow the removal.
    profile = ESXi-6.7.0-20190802001-standard
    removed = {'MEL_bootbank_nmst_4.9.0.38-1OEM.650.0.0.4598673', 'HPE_bootbank_conrep_6.7.0.03-02.00.1.7535516', 'QLC_bootbank_qedrntv_3.9.18.0-1OEM.670.0.0.7535516', 'Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.60-1OEM.550.0.0.1331820', 'HPE_bootbank_ilo_670.10.1.0.16-1OEM.670.0.0.7535516', 'HPE_bootbank_oem-build_670.U1.10.3.5-7535516', 'HPE_bootbank_amsd_670.11.3.5-6.7535516', 'HPE_bootbank_bootcfg_6.7.0.02-05.00.4.7535516', 'HPE_bootbank_ssacli_3.30.14.0-6.7.0.7535516', 'HPE_bootbank_testevent_6.7.0.02-00.01.12.7535516', 'HPE_bootbank_hponcfg_6.7.0.5.3-0.2.7535516', 'HPE_bootbank_fc-enablement_670.3.20.12-7535516', 'HPE_bootbank_smx-provider_670.03.14.00.2-7535516', 'HPE_bootbank_cru_670.6.7.10.14-1OEM.670.0.0.7535516'}
    Please refer to the log file for more details.

    [2019-08-26 21:35:00,392 root ERROR] install failed: [ProfileVibRemoval]
    You attempted to install an image profile which would have resulted in the removal of VIBs {'Cisco_Systems_Inc._bootbank_ucs-tool-esxi_1.0.2-1OEM', 'INT_bootbank_net-i40e_2.0.7-1OEM.600.0.0.2494585'}. If this is not what you intended, you may use the esxcli software profile update command to preserve the VIBs above. If this is what you intended, please use the --ok-to-remove option to explicitly allow the removal.
    profile = ESXi-6.7.0-20190802001-standard
    removed = {'Cisco_Systems_Inc._bootbank_ucs-tool-esxi_1.0.2-1OEM', 'INT_bootbank_net-i40e_2.0.7-1OEM.600.0.0.2494585'}
    Please refer to the log file for more details.

  2. Reply Vivi The Mage Aug 31,2019 2:10 pm

    You have Cisco UCS you are loading this on? I would say wait for an official Cisco release. The only reason I load them from Vmware now, is because HP Gen8 are no longer getting official HPE vmware ISO’s. Performance has held up well on my Microserver though, I have needed to make sure I get the correct VIB’s to keep performance on the disks up.

Leave a Reply

  

  

  

This site uses Akismet to reduce spam. Learn how your comment data is processed.