Red Hat SummitChapter 1. Introduction
This document provides a workflow to help keep your Red Hat OpenStack Platform 16.1 environment updated with the latest packages and containers.
This guide provides an upgrade path through the following versions:
| Old OpenStack Version | New OpenStack Version |
|---|---|
| Red Hat OpenStack Platform 16.0 | Red Hat OpenStack Platform 16.1.z |
| Red Hat OpenStack Platform 16.1 | Red Hat OpenStack Platform 16.1.z |
1.1. High level workflow
The following table provides an outline of the steps required for the upgrade process:
| Step | Description |
|---|---|
| Updating the undercloud | Update the undercloud to the latest OpenStack Platform 16.1.z version. |
| Updating the overcloud | Update the overcloud to the latest OpenStack Platform 16.1.z version. |
| Updating the Ceph Storage nodes | Upgrade all Ceph Storage services. |
| Finalize the upgrade | Run the convergence command to refresh your overcloud stack. |
If you have a multistack infrastructure, update each overcloud stack completely, one at a time. If you have a distributed compute node (DCN) infrastructure, update the overcloud at the central location completely, and then update the overcloud at each edge site, one at a time.
Considerations before you update your RHOSP environment
To help guide you during the update process, consider the following information:
- Red Hat recommends backing up the undercloud and overcloud control planes. For more information about backing up nodes, see Backing up and restoring the undercloud and control plane nodes.
- Familiarize yourself with the known issues that might block an update.
-
To identify your current maintenance release, run
$ cat /etc/rhosp-release. You can also run this command after updating your environment to validate the update.
1.2. Known issues that might block an update
Review the following known issues that might affect a successful minor version update.
Overcloud nodes that run Pacemaker version 2.0.3-5.el8_2.4 might fail to update successfully because of a race condition that occurs when shutting down the cluster on a node.
If Pacemaker version 2.0.3-5.el8_2.4 is currently installed on any of the overcloud nodes, to avoid BZ#1973660, you must upgrade Pacemaker before you can update the overcloud nodes. For more information, see the following Red Hat Knowledgebase solution Update from OSP16.1 to OSP16.2 might fail to update certain HA containers.
+For nodes that run RHEL 8.2, and are based on composable roles, you must update the Database role first before you can update any other role.
A known issue causes LDAP connections to fail after an update from release 16.1.6 or earlier, to 16.1.7 or higher. With RHOSP 16.1.7, the Identity service (keystone) container mounts /etc/openldap on the host file system. If you have previously updated from RHOSP 13, old configuration files might be present in the /etc/openldap directory that will cause Identity service LDAP connection to fail.
As a workaround, run the following command on each of the controllers:
$ sudo cp /etc/openldap/ldap.conf.rpmnew /etc/openldap/ldap.conf $ sudo podman restart keystone
Network traffic that traverses from the provider network is disrupted during the ovn-controller restart if you meet the following conditions:
- Your environment has a provider network connected by floating IP or direct port on the provider network
- You update to any 16.1 release
The downtime can vary depending on the number of existing workloads. To avoid downtime, apply the workaround in Red Hat Knowledgebase solution Data plane disruption during update/upgrade from OSP older than 16.2.2, including all 16.1 versions.
