Prechecks during preparation for an SDDC upgrade to 5.x can give an error with the message:
ERROR vSphere SHA-1 validation failedHigh: Do not perform upgrade without addressing this issue.Check the /var/log/vmware/vcf/operationsmanager/assessment/pythonvalidations/########-####-####-############/artifacts/vsphere-sha1-validation-execution-error-########-####-####-############.txt file for more details. If that file contains error code 'rpc_s_connection_closed' then please retry the precheck as it could not connect to verify whether weak algorithms (e.g. SHA-1) are in use on the vCenter.
SDDC Version 5.x
Referencing the log file mentioned in the error, we find a message similar to the one below:
/opt/vmware/vcf/operationsmanager/scripts/assessment/2x-migration/lib/third-party/pyvmomi-7.0.1/pyVmomi/Version.py:26: SyntaxWarning: "is" with a literal. Did you mean "=="? if isLegacy or ns is "":YYYY-MM-DD HH:MM:SS.SSSZ ERROR Error: Failed to trigger root cert refresh
vecs-cli failed. Error 382312694: Access denied, reason = rpc_s_auth_method (0x16c9a0f6).YYYY-MM-DD HH:MM:SS.SSSZ ERROR Failed to refresh vecs store. Error: Error: Failed to trigger root cert refresh
vecs-cli failed. Error 382312694: Access denied, reason = rpc_s_auth_method (0x16c9a0f6).
The key error to look for being:YYYY-MM-DD HH:MM:SS.SSSZ ERROR Failed to refresh vecs store. Error: Error: Failed to trigger root cert refresh
Within the VECS store, the refresh function has fallen out of sync; a manual refresh is required on the vCenter appliance.
# /usr/lib/vmware-vmafd/bin/vecs-cli force-refreshProceed to run the precheck once more and the error should be cleared.
The command below is useful for verification :
What it helps with:
Confirms whether the currently served vCenter certificate is SHA-1 or SHA-256
Useful before or after vecs-cli force-refresh