VMware Cloud Community
Techstarts
Expert
Expert
Jump to solution

Host Update Fails with error The host returns esxupdate error codes: -1. Unable to patch ESXi host

Install ESXi host with Plan ESXi 7.u1 ISO (VMware-VMvisor-Installer-7.0U1c-17325551.x86_64.isp)

Trying to update the ESXi host via Lifecycle manager.

Get following error message.

The host returns esxupdate error codes: -1. Check the Lifecycle Manager log files and esxupdate log files for more details.

ESX Update log, get the following error message

2021-08-20T14:52:22Z esxupdate: 2102380: esxupdate: ERROR: ValueError: Unequal config schemas share the same ID vsanhealth-7.0.1_0.30.17551050

When I use Custom Cisco ISO, get the following error

esxupdate: ERROR: ValueError: Unequal config schemas share the same ID esx-base-7.0.1_0.30.17551050

Unfortunately, https://kb.vmware.com/s/article/59257 does not apply and also this does not help

https://www.reddit.com/r/vmware/comments/gdd1bb/vcenter_70_host_update_issues/

Can someone help?

 

 

With Great Regards,
Labels (1)
0 Kudos
1 Solution

Accepted Solutions
Techstarts
Expert
Expert
Jump to solution

Hello Team,

I followed this article https://kb.vmware.com/s/article/2147284 and the problem was resolved. In case you came across this bug, can be helpful as others amazing thread on this communities.

 

With Great Regards,

View solution in original post

Tags (2)
7 Replies
pkvmw
VMware Employee
VMware Employee
Jump to solution

What does exactly your update path look like? Are you updating from Plain/Vanilla ESXi 7.0 U1 with a Cisco Image? And to which exact version you want to update to? (to 7.0 U1d?)

0 Kudos
Techstarts
Expert
Expert
Jump to solution

I install ESXi U1c with Cisco image.

Then I try to update to u1d and this where it fails.

With Great Regards,
0 Kudos
pkvmw
VMware Employee
VMware Employee
Jump to solution

Okay, so you've installed ESXi U1c with Cisco's customized image and you're trying to update via VLCM. Understood.

By any chance, have you opened a SR on this issue? (NOT saying you should, just wondering if you did)

0 Kudos
Techstarts
Expert
Expert
Jump to solution

I did opened the SR.

Support requested  me to reset VUM database as I mentioned I above, I can easily update via command line.

With Great Regards,
0 Kudos
Techstarts
Expert
Expert
Jump to solution

Hello Team,

I followed this article https://kb.vmware.com/s/article/2147284 and the problem was resolved. In case you came across this bug, can be helpful as others amazing thread on this communities.

 

With Great Regards,
Tags (2)
arkania
Contributor
Contributor
Jump to solution

This worked for me as well, thank you!

0 Kudos