Upgrade of vCenter 6.0 to 6.5

BSDguy

Member
Sep 22, 2014
168
7
18
51
Hi All

Starting to feel real stupid with this one but today I decided to upgrade my vCenter 6.0 to 6.5 since Veeam 9.5 Update 1 is available and supports this new version of vSphere.

Before starting the upgrade I ensured:

1) SSH was enabled on the vCSA 6.0 appliance
2) I set DRS on the cluster to manual mode

I then proceed to start the upgrade using the ISO but when I get to the "Connect to source appliance" step it keep telling me that the password is incorrect. I know the password is correct as I can use it to login to the PSC, web client host etc. Here is what the log says:

2017-01-21T14:10:26.159Z - info: LogLevel: debug
2017-01-21T14:10:26.259Z - info: Underlying platform for the OS is: win32
2017-01-21T14:10:26.259Z - info: Number of cpus is: 1
2017-01-21T14:10:26.259Z - info: Speed of cpus is: 2100
2017-01-21T14:10:26.260Z - info: RAM is: 4 GB
2017-01-21T14:10:26.262Z - debug: wizardTitle: {WORKFLOW_NAME} - Stage 1: Deploy appliance
2017-01-21T14:10:41.499Z - debug: wizardTitle: Upgrade - Stage 1: Deploy appliance
2017-01-21T14:10:41.499Z - info: Feature switch VUMUpgradeEnabled: true
2017-01-21T14:10:45.416Z - debug: eulaTxtUrl: eula_en.html
2017-01-21T14:10:47.417Z - debug: wizardTitle: Upgrade - Stage 1: Deploy appliance
2017-01-21T14:10:55.674Z - debug: Source VC IP address in DOM input value is: vcsa.domain.com
2017-01-21T14:10:55.674Z - debug: Source VC IP Value in data model is: vcsa.domain.com
2017-01-21T14:10:55.674Z - debug: Source VC IP Value in data model after correction is: vcsa.domain.com
2017-01-21T14:11:21.572Z - debug: Source VC IP address in DOM input value is: vcsa.domain.com
2017-01-21T14:11:21.572Z - debug: Source VC IP Value in data model is: vcsa.domain.com
2017-01-21T14:11:21.572Z - debug: Source VC IP Value in data model after correction is: vcsa.domain.com
2017-01-21T14:11:24.536Z - debug: Source VC IP address in DOM input value is: vcsa.domain.com
2017-01-21T14:11:24.552Z - debug: Source VC IP Value in data model is: vcsa.domain.com
2017-01-21T14:11:24.552Z - debug: Source VC IP Value in data model after correction is: vcsa.domain.com
2017-01-21T14:11:26.384Z - debug: Source Host IP address in DOM input value is: vcsa.domain.com
2017-01-21T14:11:26.384Z - debug: Source Host IP Value in data model is: vcsa.domain.com
2017-01-21T14:11:26.384Z - debug: Source Host IP Value in data model after correction is: vcsa.domain.com
2017-01-21T14:11:29.950Z - info: THUMBPRINT(vCenterAppliance): 72:7A:59:AC:2D:87:AA:40:C1:62:DF:EF:EF:F8:5E:DE:F6:7D:DD:19
2017-01-21T14:11:29.982Z - info: THUMBPRINT(esxiHost): 72:7A:59:AC:2D:87:AA:40:C1:62:DF:EF:EF:F8:5E:DE:F6:7D:DD:19
2017-01-21T14:11:31.928Z - debug: Got data accessing the vCenter Url: https://vcsa.domain.com:443/
2017-01-21T14:11:31.928Z - info: login() to source VC:vcsa.domain.com
2017-01-21T14:11:31.929Z - info: initializing vsphere API connection to vcsa.domain.com:443
2017-01-21T14:11:33.374Z - info: vimService apiType: VirtualCenter, version: 6.0.0
2017-01-21T14:11:33.444Z - debug: session does not exist: vcsa.domain.com, administrator@domain.local
2017-01-21T14:11:33.444Z - debug: Logging in to vcsa.domain.com:443 as administrator@domain.local
2017-01-21T14:11:33.855Z - info: Logged in to vcsa.domain.com:443 as administrator@domain.local, session: 520c34cf-d2a2-811a-1fdb-e86de8764389
2017-01-21T14:11:33.857Z - info: Login successful to source VC, IP: vcsa.domain.com
2017-01-21T14:11:33.857Z - info: login() to host managing the source VC:vcsa.domain.com
2017-01-21T14:11:33.857Z - info: initializing vsphere API connection to vcsa.domain.com:443
2017-01-21T14:11:34.015Z - info: vimService apiType: VirtualCenter, version: 6.0.0
2017-01-21T14:11:34.110Z - debug: session exists: vcsa.domain.com, administrator@domain.local, 520c34cf-d2a2-811a-1fdb-e86de8764389
2017-01-21T14:11:34.115Z - info: successfully logged out from vcsa.domain.com, administrator@domain.local, 520c34cf-d2a2-811a-1fdb-e86de8764389
2017-01-21T14:11:34.117Z - info: initializing vsphere API connection to vcsa.domain.com:443
2017-01-21T14:11:34.361Z - info: vimService apiType: VirtualCenter, version: 6.0.0
2017-01-21T14:11:34.362Z - debug: Logging in to vcsa.domain.com:443 as administrator@domain.local
2017-01-21T14:11:34.673Z - info: Logged in to vcsa.domain.com:443 as administrator@domain.local, session: 5298d05e-9b24-afed-adf8-f3bd1fe3179d
2017-01-21T14:11:34.674Z - debug: session sharing: sourceVcVim with sourceHostVim
2017-01-21T14:11:34.674Z - info: Login successful to host for source VC, IP: vcsa.domain.com:443
2017-01-21T14:11:34.675Z - info: sourceVcService: Source VC Version=6, minVersion=5.5, maxVersion=6.5
2017-01-21T14:11:34.675Z - info: Source VC, version: 6.0.0, isOSLinux: true
2017-01-21T14:11:34.676Z - debug: isIp: vcsa.domain.com: false
2017-01-21T14:11:34.680Z - debug: vcsa.domain.com: dnsResolve : [ '192.168.30.9' ]
2017-01-21T14:11:34.680Z - debug: vcsa.domain.com: dnsResolve : [ '2001:xxx:xxx:30::9' ]
2017-01-21T14:11:34.682Z - debug: ips associated with vcsa.domain.com: [ '192.168.30.9', '2001:xxx:xxxx:30::9' ]
2017-01-21T14:11:34.682Z - debug: getVmWithIPFQDN: hostName vcsa.domain.com is associated with [ '192.168.30.9', '2001:xxx:xxxx:30::9' ]
2017-01-21T14:11:34.752Z - debug: token:undefined, length:28, running total:28
2017-01-21T14:11:34.756Z - debug: vm found by hostName: vcsa.domain.com
2017-01-21T14:11:34.756Z - debug: getVmWithIPFQDN numVms:17
2017-01-21T14:11:34.769Z - info: VM with hostName vcsa.domain.com: { _type: 'VirtualMachine',
_moid: 'vm-1869',
config: { template: false },
guest:
{ hostName: 'vcsa',
ipAddress: '192.168.30.9',
net: [ [Object] ] },
name: 'vCSA 6',
summary:
{ storage:
{ committed: 131628612521,
uncommitted: 6625,
unshared: 122863747072,
timestamp: 2017-01-21T14:02:17.943Z } } }
2017-01-21T14:11:34.770Z - info: VM Identifier for Source VC: vm-1869
2017-01-21T14:11:36.137Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
2017-01-21T14:11:36.139Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
2017-01-21T14:11:36.139Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
2017-01-21T14:11:36.139Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
2017-01-21T14:11:36.139Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.
2017-01-21T14:11:36.140Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.

Whats so strange is that you can see in the log before the failures that the login with the credentials worked! My forward and reverse DNS is in place, time is set correctly and the passwords are correct.

What else can I try to authenticate to get past this screen?

I am trying to upgrade a vCenter appliance 6.0 Update 2 to a 6.5 appliance (ie: not using Windows for vCenter at all anywhere).

Thanks!
 

BSDguy

Member
Sep 22, 2014
168
7
18
51
Thanks but I know my root password and I checked it by logging into the vCSA 6 appliance and it logged in just fine. I reset it anyway (in case it was expired although it didn't show as expired) and rebooted the vCSA 6 appliance and its STILL not letting me get past this step.
 

nitrobass24

Moderator
Dec 26, 2010
1,088
131
63
TX
You can't upgrade vCenter from 6.0 to 6.5 using this method.
I think he was suggesting checking for updates (read: patches) for the vcsa prior to upgrading using the ISO.

Anyways glad you got it sorted.


Sent from my iPhone using Tapatalk
 

BSDguy

Member
Sep 22, 2014
168
7
18
51
Thanks but it isn't sorted ;-(

My vCenter 6 appliance is already on the latest version and checking for updates doesn't do anything as I am fully patched.

I still can't upgrade to 6.5 as it keeps saying:

2017-01-21T15:50:36.726Z - error: Failed to login to vcsa.domain.com:443 as root: ServerFaultCode: Cannot complete login due to an incorrect user name or password.
2017-01-21T15:50:36.728Z - error: Login failed for host managing source VC: ServerFaultCode: Cannot complete login due to an incorrect user name or password.

And yes, I can login to the vCSA console with the root password and it works. Argh!
 

BSDguy

Member
Sep 22, 2014
168
7
18
51
I've tried just about every combination I can think of by using root and/or administrator@domain.local.

The closest I have come is by using the following:

Source appliance: administrator@bsdpanic.local

ESXi host or vCenter Server that manages the source appliance: root (I've tried both ESXi host and vCenter)

I just don't get it, all my passwords have been tested and have authenticated me just fine but they keep getting rejected during the step.
 
  • Like
Reactions: NetWise

nitrobass24

Moderator
Dec 26, 2010
1,088
131
63
TX
I remembered one issue I had was DNS, even though it was setup properly and could verify it worked from the cli.

Once I used all IP addresses in lieu of host names I got my past my errors.


Sent from my iPhone using Tapatalk
 

BSDguy

Member
Sep 22, 2014
168
7
18
51
Ok, just tried using the IPv4 address for the vCSA 6 appliance and for the ESXi host the appliance is running on and same error.
 

BSDguy

Member
Sep 22, 2014
168
7
18
51
Heh, I'm out of ideas too. Thanks for the help.

I am running dual stack IPv4/IPv6 with vCenter and ESXi hosts.
 

BSDguy

Member
Sep 22, 2014
168
7
18
51
Already done that. Even tried vMotioning the vCSA to the other ESXi server and that didn't work either.
 

marcoi

Well-Known Member
Apr 6, 2013
1,454
245
63
Gotha Florida
Did you try SSH login directly into vcenter and try logging in with root user?

Vcenter has two passwords, the administrator@domain.local and also the root user which is need for SSH login. Just making sure you can login with both.

Also a stupid issue: Does the machine you are trying to do the update from able to ping the server using the DNS name?
 

BSDguy

Member
Sep 22, 2014
168
7
18
51
Thanks, yes, I am able to SSH into the vCSA with the root password (I just tried it now to make sure).

And yes, I can ping the ESXi hosts AND the vCSA by name from my managment server and they resolve the names and reply (both IPv4 and IPv6).
 
Dec 30, 2016
99
19
8
42
Already done that. Even tried vMotioning the vCSA to the other ESXi server and that didn't work either.
So for "ESXi host or vCenter Server" you're inputing the ESXi host name or IP that the source VCSA is running on and putting in the root credentials for the ESXi host? That's what it's asking for. In your screenshot you've entered the source VCSA hostname in that field which isn't what it wants.

Verify you can SSH into the ESXi host with those credentials as well.
 

BSDguy

Member
Sep 22, 2014
168
7
18
51
So for "ESXi host or vCenter Server" you're inputing the ESXi host name or IP that the source VCSA is running on and putting in the root credentials for the ESXi host? That's what it's asking for. In your screenshot you've entered the source VCSA hostname in that field which isn't what it wants.

Verify you can SSH into the ESXi host with those credentials as well.
Correect, I have tried using the ESXi host AND vCenter Server in the "ESXi host or vCenter Server" where the CURRENT vCSA 6 appliance is running. In the screenshot I was trying to use the vCSA in that example but I have tried using the ESXi host with it's root password unsuccessfully. I have just tried to SSH into the ESXi1 host with the root password and it worked fine.

So I have just tried using the following credentials:

upload_2017-1-21_17-4-5.png

and these is what appears in the log:

2017-01-21T17:02:58.188Z - info: VM with hostName vcsa.domain.com: { _type: 'VirtualMachine',
_moid: '387',
config: { template: false },
guest:
{ hostName: 'vcsa',
ipAddress: '192.168.30.9',
net: [ [Object] ] },
name: 'vCSA 6',
summary:
{ storage:
{ committed: 131628322022,
uncommitted: 6625,
unshared: 131628322022,
timestamp: 2017-01-21T16:55:48.162Z } } }
2017-01-21T17:02:58.188Z - info: VM Identifier for Source VC: 387
2017-01-21T17:03:00.092Z - debug: initiateFileTransferFromGuest error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
2017-01-21T17:03:00.094Z - debug: Failed to get fileTransferInfo:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
2017-01-21T17:03:00.094Z - debug: Failed to get url of file in guest vm:ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
2017-01-21T17:03:00.094Z - error: Error in getting fileData for nodeType. Error: ServerFaultCode: Failed to authenticate with the guest operating system using the supplied credentials.
2017-01-21T17:03:00.095Z - error: Failed to read the nodetype, Error: Failed to authenticate with the guest operating system using the supplied credentials.
2017-01-21T17:03:00.095Z - error: Root login failed for source VC: Failed to authenticate with the guest operating system using the supplied credentials.