You can upgrade your deployed cloud extensibility proxy, so you can access the latest functionality for your vRealize Orchestrator and on-premises extensibility action integrations.

Upgrading the cloud extensibility proxy is only supported if you are using a proxy downloaded and deployed during the vRealize Automation Cloud December 2020 release or later.

Prerequisites

  1. Download the upgrade ISO image by navigating to the MyVMware Patch Downloads page and selecting vRealize Automation Cloud Extensibility Proxy from the list of available product patches. For more information on accessing the MyVMware Patch Downloads page, see KB 80305.
  2. Connect the CD-ROM drive of the cloud extensibility proxy virtual machine in vSphere. See the vSphere Virtual Machine Administration documentation.
    Note: After connecting the CD-ROM drive, navigate to your cloud extensibility proxy VM settings page and verify that Connect At Power On is enabled.
  3. Mount the ISO image to the CD-ROM drive of the cloud extensibility proxy virtual machine in vSphere. See the vSphere Virtual Machine Administration documentation.

Procedure

  1. Log in to the cloud extensibility proxy command line as root.
  2. Run the blkid command, and note the device name for the cloud extensibility proxy CD-ROM drive.
  3. Mount the CD-ROM drive. 
    mount /dev/xxx /mnt/cdrom
  4. Back up your cloud extensibility proxy by taking a virtual machine (VM) snapshot. See Take a Snapshot of a Virtual Machine.
    Caution: The cloud extensibility proxy does not currently support memory snapshots. Before taking the snapshot of your cloud extensibility proxy, verify that the Snapshot the virtual machine’s memory option is disabled.
  5. To initiate the upgrade, run the vracli upgrade exec -y --repo cdrom:// command.
    During the upgrade, you are automatically logged out of your terminal, because the cloud extensibility proxy reboots.
  6. Log in to the cloud extensibility proxy command line as root and follow the upgrade progress by running the vracli upgrade status --follow command.
    Caution: The vracli upgrade status --follow command can occasionally display a false error message that indicates that the upgrade has failed. To troubleshoot this problem, see step 7.
  7. (Optional) If you receive an error message while running the vracli upgrade status --follow command, follow these steps:
    1. Verify that you receive the following error message: 
      Running health check after upgrade for nodes and pods.
Health check after upgrade for nodes and pods failed.
... Upgrade terminated due to critical error. Follow the upgrade guide to recover the system. ...
    2. Navigate to the /var/log/vmware/prelude/upgrade-report-latest and confirm that you receive the follwing error: 
      Pod: vco-app-xxxx is not in Ready or Completed state. All pods must be in either of these states
    3. Run the kubectl get pods -n prelude -w | grep -E 'vco|orchestration-ui' command and verify that the status of all 3 vco-app pods and the orchestration-up-app pod is RUNNING.
      Note: It can take up to 5-10 minutes after receiving the error message for all pods to enter the RUNNING state. 
      orchestration-ui-app-xxxx    1/1     Running   0          5h42m
vco-app-xxxx              3/3     Running   0          5h47m
    4. Run the curl -k https://<cloud extensibliy proxy FQDN>/vco/api/healthstatus command and verify that the health check is returning a RUNNING status. 
      {"state":"RUNNING","health-status":{"state":"OK","time":1615296823325},"instance-id":"cloud extensibility proxy FQDN"}
      Important: The preceding command must run in an environment different from the cloud extensibility proxy command line. You can run the command from the command line of a different virtual machine. You can also view the health status information in a browser by navigating directly to https:// <cloud extensibliy proxy FQDN>/vco/api/healthstatus.

Results

You have successfully upgraded your cloud extensibility proxy to the latest version.