Hi All,
I am not that experienced in VMware but I am currently having an issue when attempting to upgrade my current VCSA 6.5 U2b (Build 8815520) to VCSA 6.7 Update 3 (Build 14367737).
Just got to the Pre-Upgrade checks on the new appliance when it fails with a Single Sign-On error and Points me to a KB 2121701.
The KB is for VCenter 6.0 and I have searched around and attempted to update the SSL Trust anchors but I feel like i am going around in circles.
Any suggestions would be appreciated to try and resolve otherwise I might jsut have to burn current VCSA and set this 6.7 as new.
Thanks in advance for your help.
This can be corrected by using the 'lsdoctor' Tool.
In this case you will have to use "python lsdoctor.py -t"
____________________________________________________________________________________________________________________________________________________
"Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"
Hey OBITJarrod,
Basically the issue that you are experiencing is that the PSC Certificate or the vCenter one (Machine SSL) has not been updated correctly on the Lookup Service. That KB is applicable for vSphere 6.x. Only the first step before the resolution mentions vSphere 6.0.
I would suggest to go step by step on the KB reading carefully and in case doubts to raise a support ticket with VMware.
Actually from HPE vSphere 6.7 is not supported for that blade.
VMware from HPE Certification and Support | Hewlett Packard Enterprise
Moderator: Thread moved to the vSphere Upgrade & Install area.
This can be corrected by using the 'lsdoctor' Tool.
In this case you will have to use "python lsdoctor.py -t"
____________________________________________________________________________________________________________________________________________________
"Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"
Thanks heaps, that tool worked like a charm.
After running it the pre-upgrade checks passed and upgraded to 6.7
Where can I download lsdoctor
@infinicdl
You can find the tool in the Attachments pane of the KB article that's mentioned in the solution.
André