OPERATIONAL DEFECT DATABASE
...
...
The certificate-manager.log file is located at these locations. Windows vCenter Server C:\ProgramData\VMware\vCenterServer\logs\vmca\certificate-manager.logvCenter Server Appliance 6.x: /var/log/vmware/vmcad/certificate-manager.log Replacing the Machine SSL Certificate or Solution User Certificates with Custom CA Certificates fails at 0%.The vSphere 6.0 Certificate Manager displays an error similar to: Status : 0% Completed [Publishing Root cert...]Status : 0% Completed [Operation failed, performing automatic rollback]Error while replacing Machine SSL Cert, please see C:\ProgramData\VMware\vCenterServer\logs\vmca\certificate-manager.log for more information. Performing rollback of Machine SSL Cert... The certificate-manager.log file indicates that the dir-cli command to publish the trusted cert failed and you see entries similar to: <YYYY-MM-DD>T<time> INFO certificate-manager</time> Running command : ['C:\\Program Files\\VMware\\vCenter Server\\vmafdd\\dir-cli.exe', 'trustedcert', 'publish', '--cert', 'C:\\certs\\machineSSL\\cachain.cer', '--password', '*****'] <YYYY-MM-DD>T<time> INFO certificate-manager Command output :- <YYYY-MM-DD>T<time> ERROR certificate-manager <YYYY-MM-DD>T<time> ERROR certificate-manager Error while replacing Machine SSL Cert, please see C:\ProgramData\VMware\vCenterServer\logs\vmca\certificate-manager.log for more information. <YYYY-MM-DD>T<time> ERROR certificate-manager { "resolution": null, "detail": [ { "args": [ "" ], "id": "install.ciscommon.command.errinvoke", "localized": "An error occurred while invoking external command : ''", "translatable": "An error occurred while invoking external command : '%(0)s'" }, "Error while publishing cert using dir-cli." </time></time></time></time>], "componentKey": null, "problemId": null } Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.The certificate-manager.log file is located in these locations: Windows vCenter Server 6.x: C:\ProgramData\VMware\vCenterServer\logs\vmca\certificate-manager.logvCenter Server Appiance 6.x: /var/log/vmware/vmcad/certificate-manager.log
All Intermediate(s) and the Root CA certificates must be published into the trusted store in VMware Endpoint Certificate Store for the script to complete. Note: This issue can also be caused by using non-Base64 certificates. For more information on creating certificates, see Creating a Microsoft Certificate Authority Template for SSL certificate creation in vSphere 6.x/7.x (2112009).
This issue is resolved in VMware vCenter Server 6.0.0b, available at VMware Downloads. For more information, see the VMware vCenter Server 6.0.0b Release Notes. Process to manually publish the full chain to the VMware Endpoint Certificate Store: To work around this issue, manually publish the full chain to the VMware Endpoint Certificate Store: For Windows vCenter Server 6.x: Click Start > Run, type cmd and press Enter.Add the certificate to the VMware Endpoint Certificate Store with this command: "C:\Program Files\VMware\vCenter Server\vmafdd\dir-cli.exe" trustedcert publish --chain --cert path_to_chain.cer Note: The path_to_chain.cer is the complete path to the full chain of Intermediate CA(s) and Root CA. Enter the password for administrator@vsphere.local when prompted.Run the certificate replacement option again.When the Certificate Manager asks for the signing certificate provide just the Root CA certificate and not the full chain of CA certificates. For example: Please provide the signing certificate of the Machine SSL certificate File : "C:\certs\machineSSL\root_ca.cer" For vCenter Server Appliance 6.x: If the certificates are not currently on the vCenter Server Appliance copy them to a directory on the file system such as /root using a utility such as WinSCP or Filezilla. Note: VMware does not endorse or recommend any particular third-party utility, nor is the list above meant to be exhaustive. Connect to the vCenter Server Appliance through the console and press ALT+F1.Log in using the root user and password.Type shell.set --enabled true and press Enter.Type shell and press Enter.Add the certificate to the VMware Endpoint Certificate Store with this command: /usr/lib/vmware-vmafd/bin/dir-cli trustedcert publish --chain --cert path_to_chain.cer Enter the password for administrator@vsphere.local when prompted.Run the certificate replacement option again.When the Certificate Manager asks for the signing certificate provide just the Root CA certificate and not the full chain of CA certificates. For example: Please provide the signing certificate of the Machine SSL certificate File : "/root/root_ca.cer"
For more information, see: Replacing a vSphere 6.x Machine SSL certificate with a Custom Certificate Authority Signed CertificateReplacing default certificates with CA signed SSL certificates in vSphere 6.xReplace the Root Certificate (Intermediate CA)Custom certificate replacement fails after upgrading to vCenter Server Appliance 6.5 Update 1 For translated version of this article, see: Certificate Manager 替换证书在 0% 时失败： 操作失败，正在执行自动回滚VMware vSphere 6.0 Certificate Manager を使用して証明書を置き換えようとすると、0% の時点で次のエラーを表示して失敗する： 操作に失敗しました。自動ロールバックを実行します
Click on a version to see all relevant bugs
VMware Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
