operationsmanager.log in the SDDC Manager (/var/log/vmware/vcf/operationsmanager/operationsmanager.log) reports the SAN name for one or more of the NSX manager node as incorrect.YYYY-MM-DDTHH:SS DEBUG [vcf_om,68eaa###########################,cdec] [c.v.v.c.s.f.i.CertificateOperationsFacadeImpl,http-nio-127.0.0.1-7300-exec-6] DomainCertificateOperation: {"workflowId":"c4a504a9-####-####-####-############","domainName":"<SDDC_domain_name>","operationType":"GENERATE_CSR","operationStatus":"FAILED","resourceCertificateOperations":[{"resource":{"hostName":"<NSX_Manager_Node_FQDN>","resourceType":"nsxt_manager","master":false},"result":{"status":"FAILED","message":"{\"code\":\"CERTIFICATE_CSR_GEN_FAILED\",\"args\":[\"*****\",\"I/O error on GET request for \\\"https://<NSX_Manager_Node_FQDN>/api/v1/cluster/nodes/deployments\\\": Certificate for <NSX_Manager_Node_FQDN> doesn't match any of the subject alternative names: [<Incorrect_NSX_Manager_Node_SAN>,<NSX_Manager_Node_IP_Address>]\"]}"},"creationTimestamp":176#########,"updateTimestamp":176##########}],"retryOperation":false}
upgrade-coordinator.log in the problematic NSX Manager node (/var/log/upgrade-coordinator/upgrade-coordinator.log) will have the following snippets.YYYY-MM-DDTHH:SS ERROR task-executor-13-1-workitem-EDGE-51ac####-####-####-####-############ UpgradeAgentMessagingServiceImpl 3594 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP30033" level="ERROR" subcomp="upgrade-coordinator"] Download and verify bundle failed on node 51ac####-####-####-####-############. Failure msg: * Trying (with httplib) <NSX_Manager_Node_FQDN>:443...* certificate verification 45f3c########################### from <NSX_Manager_Node_FQDN>:443 failed: SSL: no alternative certificate subject name matches target host name '<NSX_Manager_Node_FQDN>'* Closing connection 0 curl_wrapper: (51) SSL: no alternative certificate subject name matches target host name '<NSX_Manager_Node_FQDN>'
Note: Take backup of the NSX Manager nodes before proceeding.
(1) If the NSX Manager nodes are using self-signed certificate:
(2) If the NSX Manager nodes are using custom certificate:
vcf user and then issue the su - command to switch to the root user.KEY=$(cat /etc/vmware/vcf/commonsvcs/trusted_certificates.key)
echo $KEY
keytool -importcert -alias <aliasname> -file <certificate_file_path> -keystore /etc/vmware/vcf/commonsvcs/trusted_certificates.store --storepass $KEY
<aliasname> can be any name.<certificat_file_path> with the full path to the certificate file that was uploaded in the step 2a.keytool -importcert -alias <aliasname> -file <root_certificate_file_path> -keystore /etc/alternatives/jre/lib/security/cacerts --storepass changeit
<aliasname> can be any name.<root_certificate_file_path> with the full path to the certificate file that was uploaded in the step 2b./opt/vmware/vcf/operationsmanager/scripts/cli/sddcmanager_restart_services.sh
keytool -list -v -keystore /etc/vmware/vcf/commonsvcs/trusted_certificates.store -storepass $KEY