Symptoms:
kubectl -n prelude get pods/services-logs/prelude/vco-app/file-logs/vco-server-app.log) such as:com.vmware.olln.security.auth.sso.ComponentManagerLookupService - Could not get Sso Endpoint information through service call. Fall back to local settings.
com.vmware.olln.cis. CisException: com.vmware.olln.cis.CisException: com.vmware.olln.cis.CisException: javax.net.ssl.SSLHandshakeException: Certificate is not in CA store or is invalid.
... Failed to instantiate ...
ERROR vco [...] {} com.vmware.o11n.service.spring.bootstrap.ServiceBootstrap - Application context initialization failed!
The new certificate for the authenticating vCenter Server is not added to the vRO trust store
Add the new vCenter certificate to the Orchestrator trust store following steps in the documentation.
The documentation page for 8.18.1 and later references using an Orchestrator workflow of "Import a trusted certificate from a file". KB article 404474 (How to import a trusted certificate to the keystore in VCO.) can be used for the steps.
If it is not possible to access the Orchestrator UI in order to add this certificate, then the authenticating vCenter can be re-registered as the authenticator via the Orchestrator shell:
vracli vro authentication wizardAlternatively this can be registered in non-interactive mode, using a command line similar to this example (this example configures vSphrere SSO for Authnetication):
vracli vro authentication set -p vsphere -hn https://my-vsphere.local -u [email protected] --tenant vsphere.local --admin-group Administrators --admin-group-domain vsphere.localFor further details on the command syntax, please see this article: Configuring the Automation Orchestrator Appliance authentication provider with the command line interface