Unable to connect to Remote Console for machines provisioned in vCenter 8.0.0 and above

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• A sever side error is observed when trying to connect to the remote console of a virtual machine provisioned in vCenter 8.0.0 and above
• provisioning-service-app logs contain the following error message

  com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: A specified parameter was not correct: ticketType Please see the server log to find more detail regarding exact cause of the failure.

Environment

VMware vRealize Automation 8.9.x
VMware vRealize Automation 8.5.x
VMware vRealize Automation 8.10.x
VMware vRealize Automation 8.6.x
VMware vRealize Automation 8.8.x
VMware vRealize Automation 8.7.x
VMware vRealize Automation 8.1.x
VMware vRealize Automation 8.0.x
VMware vRealize Automation 8.4.x
VMware vRealize Automation 8.3.x
VMware vRealize Automation 8.2.x

Cause

vCenter ended support for the older mks ticket type in version 8.0.0 and adopted the newer webmks format in its place. For vRA 8.10.1 and below the mks ticket type is still used when the remote console proxy is enabled, which leads to connection issues for vCenter endpoints with version 8.0.0 and above.

Resolution

This issue is resolved in VMware vRealize Automation 8.10.2.

Workaround:

Prerequisites

• Please take simultaneous non-memory snapshots of each virtual appliance(s) in the cluster.
• You have access to root user and password
• You have SSH or console access to each virtual appliance.

Procedure

To switch to webmks, remote console proxy should be disabled.

1. SSH / PuTTy into one vRA virtual appliance in the cluster
2. Edit the provisioning service deployment by running the following command

   kubectl -n prelude edit deployment provisioning-service-app

3. Set the following property in the JAVA_OPTS list to false

   -Denable.remote-console-proxy=false

Note: To edit, move the cursor to the line where you want to make the change, and press the i key on the keyboard to enter insert mode. Change the value.

Note: Be careful with spacing, do not use TABs.

4. Save the changes, press the escape key on the keyboard, and then save the change by pressing :wq. If you make a mistake you can exit without saving by entering :q! instead.
5. Monitor the provisioning-service-app pod restart by running watch kubectl get pods -n prelude within the vRA SSH session. Once the pods are restarted and in a Ready state, retry the VMRC connection.

Additional Information

Impact/Risks:
This is a known issue affecting vRealize Automation 8.10.1 and below.