To upgrade to VMware Integrated OpenStack 7.2.1 from 7.x, you apply a patch.


  • Create a folder VMware Integrated OpenStack download page.
  • Verify that the VMware Integrated OpenStack manager has 20 GB of free disk space. To free some disk space, you can remove the downloaded tar ball patch.
  • If you have an existing VMware Integrated OpenStack 7.x with an OpenStack deployment, create a backup of your existing deployment. See Back Up Your Deployment.
  • Applying patch cannot update the previously customized images in CR. For using the images delivered in the patch, you must remove the image related configuration by using viocli update <CR name>.
  • Before starting the patch, ensure that your VMware Integrated OpenStack deployment is in RUNNING state and mariadb cluster is not partitioned (KB 88765).


  1. Log in to the Integrated OpenStack Manager in the VMware Integrated OpenStack environment.
    ssh root@mgmt-server-ip
    Navigate to the VMware Integrated OpenStack 7.2.1 patch folder.
    cd <vio-patch-folder>
    Unpack the tarball.
    tar -zxvf vio-patch-
  2. Run the script. This script helps you do some pre-condition check and reminds you the next steps for installing the patch.
    If precheck on VMware Integrated OpenStack manager root disk usage failed, you can re-run this script with --clean-stale-patch.
    ./ --clean-stale-patch
  3. Add the patch to your VMware Integrated OpenStack manager.
    viocli patch add -l /<vio-patch-folder>/patch-<vio-patch-version>.tar.gz
    Verify that the patch has been added.
    viocli patch list

    If properly added, the state of the patch appears as: ADDED.

  4. Install the patch.
    viocli patch install -p patch-<vio-patch-version>
    Verify that the patch has been installed.
    viocli patch list

    If properly installed on an existing VMware Integrated OpenStack 7.x deployment, the state of the patch appears as: APPLIED and the apply progress appears as: 100%.

    If the patch has been applied, check the patch deployment status.
    viocli get deployment

    If the deployment is stable, the state of the deployment appears as: RUNNING, indicating that all OpenStack services have been patched.

    • If an error occurs or the deployment is not stable, retain the support bundle for tracking.
    • If VMware Integrated OpenStack is integrated with vRealize Operations Manager, you must accept the new certificate of VMware Integrated OpenStack manager by clicking the VALIDATE CONNECTION from vRealize Operations Manager after applying the VMware Integrated OpenStack 7.2.1 patch.
    • During the patch process, you can find some deployment state transitions between OUTAGE, RECONFIGURING, DEGRADED, and RUNNING.
    • If required, you can manually update Photon packages after patch as follows:
      tdnf update <photon-package-name>

      Ensure that your tdnf command is available in your VMware Integrated OpenStack manager VM or controller VM. You can setup proxy if your deployment has no access to Photon package repository.

    • After the patch is complete, you can do some basic validation. If you plan to revert the patch, ensure that you do not change the service configurations.