Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Bringup fails during vCenter Server certificate replacement in VVD on VxRail (67683)

Last Updated: 11/28/2023Categories: InformationalTotal Views: 3468Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

You see Configure Signed Certificate on vCenter Server task failed in cloud builder management console

You see messages similar to the following in the bringup log file on the Cloud Builder VM:

<---Invoking method POSTVALIDATE of task VcSignedCertificateConfiguration--->
Description: Configure Signed Certificate on vCenter Server,
ParamBuilder: param builder com.vmware.evo.sddc.bringup.adapters.toplugin.VcCertificateParamAdapter
ProcessingId: 7f000001-6973-1b09-8169-743f240500e7..
2019-03-13T21:40:17.384+0000 DEBUG [0000000000000000,0000,operationToken=<f5a35bd0-451e-11e9-b541-9306fb11c371>] [c.v.e.s.b.m.c.SelfSignedBringupCertificates,threadPoolExecutor-4] Certificate will be generated for VC
2019-03-13T21:40:17.384+0000 DEBUG [0000000000000000,0000,operationToken=<f5a35bd0-451e-11e9-b541-9306fb11c371>] [c.v.e.s.b.u.v.VcPscSignedCertificateConfiguration,threadPoolExecutor-4] Validating if thumbprint of certificate on host 10.249.236.11 matches 3E:4A:9F:96:6A:3F:7D:08:81:72:12:68:11:85:7A:D1:DD:B8:FB:91
2019-03-13T21:40:17.397+0000 DEBUG [0000000000000000,0000,operationToken=<f5a35bd0-451e-11e9-b541-9306fb11c371>] [c.v.evo.sddc.bringup.util.HttpsUtil,threadPoolExecutor-4] SSL fingerprint for host 10.249.236.11 is: 80:46:6B:B0:3A:EE:1E:30:BA:D4:8F:03:3F:C4:31:B9:F0:BB:E1:3B
2019-03-13T21:40:17.407+0000 ERROR [0000000000000000,0000] [c.v.e.s.o.model.error.ErrorFactory,threadPoolExecutor-4] [6NILN8] POSTVALIDATE_SIGNED_CERTIFICATE_CONFIGURATION_FAILED Failed to validate signed certificate configuration on 10.249.236.11
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to validate signed certificate configuration on 10.249.236.11
at com.vmware.evo.sddc.bringup.plugin.vc.action65.impl.VcSignedCertificateConfiguration.postValidate(VcSignedCertificateConfiguration.java:124)
at com.vmware.evo.sddc.bringup.plugin.vc.action65.impl.VcSignedCertificateConfiguration.postValidate(VcSignedCertificateConfiguration.java:30)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.lambda$static$2(FsmActionState.java:22)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:62)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:167)
at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:154)
at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:333)
at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:460)
at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:96)
at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:55)
at reactor.bus.EventBus$3.accept(EventBus.java:317)
at reactor.bus.EventBus$3.accept(EventBus.java:310)
at reactor.bus.routing.ConsumerFilteringRouter.route(ConsumerFilteringRouter.java:72)
at reactor.bus.EventBus.accept(EventBus.java:591)
at reactor.bus.EventBus.accept(EventBus.java:63)
at reactor.core.dispatch.AbstractLifecycleDispatcher.route(AbstractLifecycleDispatcher.java:160)
at reactor.core.dispatch.MultiThreadDispatcher$MultiThreadTask.run(MultiThreadDispatcher.java:74)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

You see messages similar to the following in the /var/log/vmware/vpxd/vpxd.log file on the vCenter Server VM:

The remote host certificate has these problems:
-->
--> * unable to get issuer certificate)
--> [context]zKq7AVECAAAAAAnxsgANdnB4ZAAAiLEqbGlidm1hY29yZS5zbwAAQDcbAI67GACa+CEAZSkiABf9IQDPASIAXVIjAJUfIwBeIiMAEQkrAdRzAGxpYnB0aHJlYWQuc28uMAACnYwObGliYy5zby42AA==[/context]

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Resolution

This is a known issue affecting VVD on VxRail. There is currently no resolution.

Workaround

Use the following steps to workaround this issue:

Copy the correct RootCA.cer and IntermediateCA.cer files to the CertGenVVD root folder on the system where the CertGenVVD utility is installed.

Rename both files such that their filename extension is .pem.

Issue the following command:

openssl verify -verbose -CAfile RootCA.pem IntermediateCA.cer
IntermediateCA.pem: OK

Note: You may see an error similar to the following if the root or one of the intermediate certificates are invalid:

IntermediateCA.pem: C = US, O = DigiCert Inc, CN = DigiCert Global CA G2
error 20 at 0 depth lookup:unable to get local issuer certificate

Once the CA certificate chain is validated, concatenate the certificates together by issuing a command similar to the following:

copy IntermediateCAroot01.cer+IntermediateCAroot02.cer+RootCA.cer > Root64.cer

Use a file transfer utility to copy the Root64.cer file to the /tmp folder on the Cloud Builder VM.

SSH to the Cloud Builder VM as the root user and then issue the su - command to switch to the root user.

Issue the following command to move the Root64.cer file from /tmp to /opt/vmware/vvd/certificates/RootCA/

mv /tmp/Root64.cer /opt/vmware/vvd/certificates/RootCA/

Issue the /opt/vmware/vvd/cloud-builder/install/reconfigure.sh command.

In the Cloud Builder UI, click the Retry button to restart the bringup process.

Related Information

Certificate Generation Utility for VMware Validated Design for Software-Defined Data Center (2146215)

To be alerted when this article is updated, click the Subscribe to Article link in the Actions box.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
HW-122016：Workspace ONE Access Connector で es-config.json パスワードの検証に失敗し、証明書が生成されない (80489)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
VIDM 用户无法向 vRealize Log Insight 4.x 进行身份验证 (54995)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Builder

Related Versions:

VMware Validated Design for Software-Defined Data Center (SDDC) 5.0.x

VMware Validated Design for Software-Defined Data Center (SDDC)

Take Our Survey

Support Assistant