In the appliance management interface, you can upgrade VMware Cloud Director Availability to the latest version by using an .iso file containing the upgrade binaries that you mount to the CD-ROM drive of the virtual appliance.

Prerequisites

  • Download the VMware-Cloud-Director-Availability-release.number.xxxxxxx-build_sha.iso file, that contains the VMware Cloud Director Availability release.number Upgrade Disk Image.

Procedure

  1. Copy the .iso file to a datastore that is accessible from the vCenter Server instance that you use with VMware Cloud Director Availability.
  2. Mount the .iso file to the appliance.
    1. Log in to the on-premises vCenter Server by using the vSphere Client.
    2. Locate the virtual machine that hosts the appliance.
    3. Right-click the virtual machine and select Edit Settings.
    4. On the Virtual Hardware tab, select CD/DVD Drive > Datastore ISO File.
    5. Follow the prompts to add the CD/DVD drive to the virtual machine and select the Connected option.
  3. By using the virtual appliance console, mount the .iso file inside the guest operating system of the appliance.
    1. Connect to the appliance console either by using a Secure Shell (SSH) client or by using the appliance console in the vSphere Client and log in as the root user.
    2. Mount the .iso file inside the guest operating system of the appliance.
      mount /mnt/cdrom
  4. Log in to the management interface of the appliance.
    1. In a Web browser, go to https://Appliance-IP-address/ui/admin.
    2. Select Appliance login or SSO login and enter the root or the single sign-on user credentials.
    3. Click Login.
  5. In the left pane, click Settings.
  6. Under Version, next to Product version click Check for updates.
  7. Upgrade the appliance by completing the Update wizard.
    Note: Proceed with the upgrade only after taking a snapshot of the appliance.
    1. On the Repository page, select Use CDROM Updates and click Next.
    2. On the Available updates page, select an update and click Next.
    3. On the EULA Review page, to accept the end-user license agreement click Next.
    4. On the Ready for update page, click Finish and wait for the installation process to finish.
  8. After the upgrade finishes, verify that the upgrade is successful.

    When the upgrade process finishes, in the left pane in System Tasks, you might see a red Update task that failed with messages like Operation aborted due to an unexpected error or Task aborted due to service reboot, while the upgrade is successful.

    1. Connect to the appliance console either by using a Secure Shell (SSH) client or by using the appliance console in the vSphere Client and log in as the root user.
    2. Open the upgrade log file.
      less /var/log/upgrade.log
    3. Verify that the upgrade log finishes with the following log extract.
      • When starting the upgrade from version 4.0.x, the appliance automatically restarts.
        Complete!
        Nothing left to do.
        ...
        The upgrade was successful! Scheduling reboot in 15 seconds..
      • When starting the upgrade from version 4.0.0.x, after the upgrade finishes you must restart the appliance.
        Complete!
        Verifying...             ########################################
        Preparing...             ########################################
        	package filesystem-1.1-4.ph3.x86_64 is already installed
        Bad exit code: 256
        {
          “code”: “BadExitCode”,
          “msg”: “”,
          “args”: [
            “256"
          ]
        }
        After you see this upgrade log extract, restart the appliance.
        reboot
  9. Unmount the .iso file.
    1. In the vSphere Client, shut down the virtual machine that hosts the appliance.
    2. Right-click the virtual machine and select Edit Settings.
    3. In the Virtual Hardware tab, select CD/DVD Drive and deselect Connected and Connect At Power On.
    4. Power on the virtual machine that hosts the appliance.

What to do next

After you upgrade the appliance, complete the upgrade with a post-upgrade configuration. For more information, see Post-Upgrade Configuration.