VMware Cloud Community
Toreft
Contributor
Contributor

Dependency error while upgrading from 6.0 to 6.5

I am trying to upgrady a IBM vm server from 6.0 to 6.5 i have an IBM System x3650 M4 : -[7915E3G] with Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz

This is what i do:

[root@vm:~]esxcli software profile update -p ESXi-6.5.0-4564106-no-tools -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

[DependencyError]

VIB Emulex_bootbank_scsi-be2iscsi_4.1.334.3-1OEM.500.0.0.472629 requires com.vmware.iscsi_linux-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

VIB Brocade_bootbank_net-bna_3.0.3.0-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

VIB Brocade_bootbank_net-bna_3.0.3.0-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

VIB Brocade_bootbank_scsi-bfa_3.0.3.0-1OEM.500.0.0.472560 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMware_bootbank_net-qlge_1.0.0.47-1vmw.500.0.0.406165 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

VIB Emulex_bootbank_scsi-be2iscsi_4.1.334.3-1OEM.500.0.0.472629 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMware_bootbank_scsi-qla4xxx_624.01.36-1vmw.500.0.0.406165 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

VIB Emulex_bootbank_scsi-be2iscsi_4.1.334.3-1OEM.500.0.0.472629 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMware_bootbank_net-qlge_1.0.0.47-1vmw.500.0.0.406165 requires com.vmware.driverAPI-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

VIB Brocade_bootbank_scsi-bfa_3.0.3.0-1OEM.500.0.0.472560 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMware_bootbank_scsi-qla4xxx_624.01.36-1vmw.500.0.0.406165 requires com.vmware.iscsi_linux-9.2.0.0, but the requirement cannot be satisfied within the ImageProfile.

VIB VMware_bootbank_scsi-qla4xxx_624.01.36-1vmw.500.0.0.406165 requires vmkapi_2_0_0_0, but the requirement cannot be satisfied within the ImageProfile.

Please refer to the log file for more details.

[root@GGRvm02:~] esxcli software sources profile list -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml | grep -i ESXi-6.5

ESXi-6.5.0-20170104001-standard   VMware, Inc.  PartnerSupported

ESXi-6.5.0-20170104001-no-tools   VMware, Inc.  PartnerSupported

ESXi-6.5.0-4564106-standard       VMware, Inc.  PartnerSupported

ESXi-6.5.0-4564106-no-tools       VMware, Inc.  PartnerSupported

Any Ide on how to get this working?

Regards

Tore

tail -n 30 /var/log/esxupdate.log (attached)

5 Replies
vvermani
Contributor
Contributor

Try to add a -f  at the end of your command or use a local depot, see command below:

esxcli software profile update -d <location of the offline bundle> -p <Profile Name> -f

E.g.

esxcli software profile update -d /vmfs/volumes/datastore1/VMware-ESXi-6.5.0-OS-Release-4564106-HPE-650.9.6.0.28-Nov2016-depot.zip -p HPE-ESXi-6.5.0-OS-Release-650.9.6.0.28 -f

Note: It Bypasses checks for package dependencies, conflicts, obsolescence, and acceptance levels. It is not recommended unless you know what you are doing. Use of this option will result in a warning being displayed in the vSphere Client.

Thanks, VV
Reply
0 Kudos
Toreft
Contributor
Contributor

Hi!

Thanks for answering.

So I tried with local repo and got same errors, but i do not want to try forcing and ignoring error messages as this is prod.

How can i determine what is wrong and how to fix this?

Regards

Tore

nolame
Contributor
Contributor

Hello!

vvermani​ Thank u for the solution! I tried to do so, but did not help.

After update and reboot the system don't see drives and after another reboot rolled back.

I have Promise raid EX8654.

Reply
0 Kudos
Naganagp
Contributor
Contributor

I was testing upgrade ESXi 6.0 to 6.5 with CLI, I got same error, added -f at the end it worked, Thank you so much for sharing your experience.

Result as below:

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

[root@localhost:~] esxcli software vib update -d /vmfs/volumes/datastore1/update-from-esxi6.5-6.5_updat

e01.zip -f

Installation Result

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

   Reboot Required: true

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

Reply
0 Kudos
tjenarvi
Contributor
Contributor

I did use -f to force upgrade from 6.0 to 6.5 but then I could not update any profile and I was stucked.

Refer to this blog --> https://www.vladan.fr/how-to-upgrade-esxi-6-0-to-6-5-via-cli-on-line/?unapproved=195886&moderation-h...

I found below working for me.

    • # esxcli software vib remove -n char-hpilo -f
      # esxcli software vib remove -n char-hpcru -f
      # esxcli software vib remove -n ehci-ehci-hcd -f
      # esxcli software vib remove -n net-mst
      # esxcli software vib install -d hpe-esxi6.5uX-bundle-2.6.2-2.zip

I have no idea why do I have to remove those dependencies, char-hpilo, char-hpcru, ehci-ehci-hcd, net-mst.

What are those vibs ?

    • Then finally I could update it !!
      # esxcli software vib update -d ESXi650-201703001.zip

Reply
0 Kudos