DawitBirhanu
Enthusiast
Enthusiast

VCenter Upgrade from 6.5 U2b to 6.7 U1 Failed with 'Failed to send http data'

Jump to solution

DNS entries are all good. Both forward and reverse for source ESXi, source PSC, destination ESXi are correct.

My setup is VCSA with external PSC in a VSAN.

The plan was to first upgrade external PSC followed by upgrading VC and then migrating to an embedded PSC.

It filed on the first phase (VCSA deployment) of external PSC upgrade. Here is what I did:

Launched the VCSA GUI installer and selected Upgrade. Then I entered the source appliance FQDN and clicked connect. Then populated the ESXi host and PSC details as shown below:

pastedImage_0.png

Pressed NEXT and accepted the thumbprints of the certificates on the next screen. Then entered the target ESXi host detail on the next screen as shown below:

pastedImage_1.png

Pressed NEXT and accepted the thumbprints of the certificates on the next screen. And populated the next screen as shown below.

pastedImage_3.png

On the next screen, I Selected Data Store.

In the "Configure network setting" screen selected the right network, and entered static temporary IP, default gateway and DNS server. Then pressed NEXT.

In the "Ready to complete stage 1" I verified the settings and pressed FINISH. Then I got the error message shown below:

pastedImage_4.png

The installed log pointed the error message is attached.

Some of the error entries in the log are shown below. 10.20.0.121 is the temporary IP address for the PSC.

2019-03-18T15:19:53.330Z - warn: DNS is not resolved to IPv6: Error: queryAaaa ENODATA psc1.xxxxxxxxxx.com

...

2019-03-18T15:22:13.939Z - error: ServerFaultCode: 'VSAN.EnableVsanBootstrap' is invalid or exceeds the maximum number of characters permitted.

...

2019-03-18T15:27:22.680Z - error: No VM found with hostname 10.20.0.121

2019-03-18T15:27:22.680Z - debug: Error in getVmWithIPFQDN: No VM found with hostname 10.20.0.121

I appreciate help with troubleshooting this issue.

0 Kudos
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership

From how I understand it, it's only v6.5 U2d and later with are currently not supported for an upgrade to v6.7, so that shouldn't be the root cause in this case.

Anyway, you may want to check whether specifying the ESXi host's IP address, rather than it's FQDN will help (see https://www.ivobeerens.nl/2018/09/12/vcenter-server-appliance-vcsa-failed-to-send-http-data-error/).

André

View solution in original post

0 Kudos
6 Replies
daphnissov
Immortal
Immortal

That upgrade path right now is unsupported. Please see the release notes. There is no work around until update 2 is released.

0 Kudos
DawitBirhanu
Enthusiast
Enthusiast

Thank you for the quick response.

Correction: My source PSC is actually running 6.5 build number 8815520, which corresponds to 6.5 U2b and release date of June 28, 2019.

The below interoperability matrices indicate that upgrade from 6.5 U2 to 6.7 U1 is allowed under the following condition.

"Upgrade from 6.5 patches post 6.5 U2, dated November 2018 or after, to 6.7 U1 are unsupported as it is considered back-in time

VMware Product Interoperability Matrices

As per this statement my upgrade is supported. Am I missing something?

0 Kudos
daphnissov
Immortal
Immortal

Yes, you're missing exactly what you printed.

My source PSC is actually running 6.5 build number 8815520, which corresponds to 6.5 U2b

Upgrade from 6.5 patches post 6.5 U2, dated November 2018 or after, to 6.7 U1 are unsupported

U2b = post U2

0 Kudos
a_p_
Leadership
Leadership

From how I understand it, it's only v6.5 U2d and later with are currently not supported for an upgrade to v6.7, so that shouldn't be the root cause in this case.

Anyway, you may want to check whether specifying the ESXi host's IP address, rather than it's FQDN will help (see https://www.ivobeerens.nl/2018/09/12/vcenter-server-appliance-vcsa-failed-to-send-http-data-error/).

André

View solution in original post

0 Kudos
DawitBirhanu
Enthusiast
Enthusiast

Andre, you are right.

I mis-stated my from version. It is actually 6.5 U2b. I also corrected the title of the discussion to reflect the same.

I am attempting to upgrade from 6.5 U2b (released in June 201) to 6.7 U1. And it is failing.

0 Kudos
DawitBirhanu
Enthusiast
Enthusiast

Thanks Andre. Using the IP address instead of FQDN worked.

0 Kudos