Chapter 2. Performing a minor update

1. Check the Openstack version of your deployment and the available version that you can update your deployment to:

   $ oc get openstackversion
   NAME                  TARGET VERSION        AVAILABLE VERSION    DEPLOYED VERSION
   openstack-control-plane   18.0.9-20250602.2   18.0.10-20250701.2   18.0.9-20250602.2

   • The target version, 18.0.9-20250602.2, is the OpenStack version that maps to the 18.0.9 RHOSO version.
   • The available version, 18.0.10-20250701.2, is the OpenStack version that maps to the 18.0.10 RHOSO version. You use the OpenStack version to set the targetVersion field in your patch file.

2. Set the targetVersion field in your patch file, for example, openstackversionpatch.yaml:

   $ cat <<EOF >openstackversionpatch.yaml
      spec:
       targetVersion: 18.0.10-20250701.2
   ...
   EOF

Procedure

1. Create a patch file for the OpenStackVersion CR on your workstation, for example, openstackversionpatch.yaml.

2. Set the targetVersion to the release that you want to install:

   $ cat <<EOF >openstackversionpatch.yaml
       spec:
         targetVersion: <openstack_version>
         customContainerImages:
           cinderApiImage: <custom_image>
           cinderVolumeImages:
             netapp: <custom_image>
             dell: <custom_image>
   EOF

   • Replace <openstack_version> with the target version you want to install, for example, 1.0.1.
   • Replace <custom_image> with the location of the latest custom image for the service. You must update the image location for any custom images and the target version at the same time to ensure that the correct custom image is used after the minor update is complete.

3. Patch the OpenStackVersion CR:

   $ oc patch openstackversion <openstack_version_CR_name> --type=merge --patch-file openstackversionpatch.yaml

   • Replace <openstack_version_CR_name> with the name of your OpenStackVersion resource, for example, openstack-control-plane.

4. Verify that the OVN services are updated on the control plane:

   $ oc wait openstackversion <openstack_version_CR_name> --for=condition=MinorUpdateOVNControlplane  --timeout=20m

   The following example output shows that the OVN services are updated:

   openstackversion.core.openstack.org/<openstack_version_CR_name>
   condition met

Procedure

1. To update OVN services on the data plane, create an OpenStackDataPlaneDeployment custom resource (CR) with the openstack-edpm-update-ovn.yaml file:

   $ oc create -f openstack-edpm-update-ovn.yaml

2. Verify that the data plane update deployment succeeded:

   $ oc wait openstackversion <openstack_version_CR_name> --for=condition=MinorUpdateOVNDataplane --timeout=20m

   $ oc get openstackdataplanedeployment
   NAME             			     STATUS  MESSAGE
   edpm-deployment-ipam   		             True  Setup Complete
   edpm-deployment-ipam-ovn-update              True  Setup Complete

   • Replace <openstack_version_CR_name> with the name of your OpenStackVersion resource, for example, openstackversion/openstack.

     If the deployment fails, see Troubleshooting data plane creation and deployment in the Deploying Red Hat OpenStack Services on OpenShift guide.

Procedure

1. Create an OpenStackDataPlaneDeployment custom resource (CR) with the openstack-edpm-update-services.yaml file:

   $ oc create -f openstack-edpm-update-services.yaml

2. Verify that the data plane update deployment succeeded:

   $ oc wait openstackversion <openstack_version_CR_name> --for=condition=MinorUpdateDataplane --timeout=20m

   $ oc get openstackdataplanedeployment
   NAME             	                        STATUS  MESSAGE
   edpm-deployment-ipam   	                        True  Setup Complete
   edpm-deployment-ipam-update 	                True  Setup Complete
   edpm-deployment-ipam-update-dataplane-services  True  Setup Complete

   If the deployment fails, see Troubleshooting data plane creation and deployment in the Deploying Red Hat OpenStack Services on OpenShift guide.