Synchronizing workflows from vCO 5.5.x to vRO 7.0.x fails

Products

• VMware Aria Suite

Issue/Introduction

Synchronizing workflows from vCenter Orchestrator 5.5.x to vRealize Orchestrator 7.0.x fails and it can be resolved by enabling TLSv protocol in vRealize Orchestrator appliance.

Symptoms:

• Unable to synchronize workflows from vCenter Orchestrator 5.5.x to vRealize Orchestrator 7.0.x.
• You see an error:
  
  org.springframework.remoting.RemoteAccessException: Could not access HTTP invoker remote service at [https:// vrealize-orchestrator-fqdn:8281https://vrealize-orchestrator-fqdn:8281/vco]; nested exception is javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
  

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

Environment

VMware vRealize Orchestrator 7.0.x
VMware vCenter Orchestrator 5.5.x

Cause

This issue occurs when vCenter Orchestrator attempts to establish a connection to remote host using TLSv1 protocol which is disabled in vRealize Orchestrator 7.0.x due to security reasons.

Resolution

To resolve the issue, enable TLSv1 protocol in the vRealize Orchestrator appliance.

To enable TLSv1 protocol in vRealize Orchestrator appliance:

1. Take a snapshot of vRealize Orchestrator appliance.
2. Connect to the vRealize Orchestrator appliance using SSH.
3. Open the /etc/vco/app-server/server.xml file using a text editor.
4. Add the TLSv1 protocol to the sslEnabledProtocols field.
   
   It should appear as sslEnabledProtocols="TLSv1, TLSv1.1, TLSv1.2" .
   
   
5. Restart the Orchestrator service by running the command:
   
   service vco-server restart