Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 2. Performing a minor update

To update your Red Hat OpenStack Services on OpenShift (RHOSO) 18.0 environment to the latest maintenance release, perform the following tasks:

  1. Update OVN services on the control plane.
  2. Update OVN services on the data plane.
  3. Wait for the OpenStack Operator to complete the automatic update of the remaining control plane packages, services, and container images.
  4. Update the remaining services on the data plane.

During the minor update, you must create a patch file of your OpenStackVersion custom resource (CR) and set the target version to the latest available OpenStack version that is provided by the openstack-operator. The following example shows an environment that is being updated from Red Hat OpenStack Services on OpenShift (RHOSO) 18.0.9 to RHOSO 18.0.10.

  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

2.2. Updating OVN services on the control plane
Copier lien

Update the target version in the OpenStackVersion custom resource (CR) to point to the version that you want to install. After you update the target version, the OVN service update on the control plane begins automatically.

Prerequisites

  • You have the name and version of your OpenStackControlPlane CR: 

    $ oc get openstackversion
NAME                  TARGET VERSION        AVAILABLE VERSION    DEPLOYED VERSION
openstack-control-plane  18.0.0-20240828.1   18.0.2-20240923.2  18.0.0-20240828.1

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

2.3. Updating OVN services on the data plane
Copier lien

Update the OVN services on the data plane.

Prerequisites

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.

Important

If the update fails, you can re-run the procedure. Before you re-run the procedure, you must edit the name: parameter in the openstack-edpm-update-ovn.yaml file to avoid conflicts in the CR name. For example: 

apiVersion: dataplane.openstack.org/v1beta1
kind: OpenStackDataPlaneDeployment
metadata:
  name: <ovn-update-new-name>
...
  • Replace <ovn-update-new-name> with a unique name for the CR.

2.4. Verifying the control plane services update
Copier lien

Verify that the automatic update of the control plane services is complete before you begin updating the remaining services on the data plane.

Procedure

  • Wait until all control plane services are updated: 

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

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

      The command returns the following output when all the control plane services are updated: 

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

2.5. Updating the remaining services on the data plane
Copier lien

When the OVN service is updated on the control plane and data plane, and the OpenStack Operator has completed the automatic update of the remaining control plane packages, services, and container images, you must update the remaining services on the data plane.

Prerequisites

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.

Troubleshooting

If the update fails, you can re-run the procedure. Before you re-run the procedure, you must edit the name: parameter in the openstack-edpm-update-services.yaml file to avoid conflicts in the CR name. For example: 

apiVersion: dataplane.openstack.org/v1beta1
kind: OpenStackDataPlaneDeployment
metadata:
  name: <services-update-new-name>
...
  • Replace <services-update-new-name> with a unique name for the CR.
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2026 Red HatRetour au début