Chapter 11. Upgrading the overcloud
Upgrade Red Hat OpenStack Platform content across the whole overcloud on each stack in your environment.
11.1. Upgrading RHOSP on all nodes in each stack Copy linkLink copied to clipboard!
Upgrade all overcloud nodes to Red Hat OpenStack Platform (RHOSP) 17.1 for each stack, starting with the main stack.
You must ensure that the pacemaker is running on all controllers before you upgrade the overcloud nodes.
For information about the duration and impact of this upgrade procedure, see Upgrade duration and impact.
Procedure
-
Log in to the undercloud host as the
stack
user. Source the
stackrc
undercloud credentials file:source ~/stackrc
$ source ~/stackrc
Copy to Clipboard Copied! Toggle word wrap Toggle overflow If you do not have a DCN or multi-cell deployment that includes ML2/OVN, upgrade RHOSP on all nodes in your main stack:
openstack overcloud upgrade run --yes --stack <stack> --debug --limit allovercloud,undercloud --playbook all
$ openstack overcloud upgrade run --yes --stack <stack> --debug --limit allovercloud,undercloud --playbook all
Copy to Clipboard Copied! Toggle word wrap Toggle overflow ImportantDo not modify the
--limit
option. You must upgrade all nodes in the stack at once to avoid breaking your workloads. If you need assistance, contact Red Hat Support.Replace
<stack>
with the name of the overcloud stack that you want to upgrade the nodes on.Repeat this step for each stack in your RHOSP deployment.
If you have a DCN or multi-cell deployment that includes ML2/OVN, upgrade the OVN containers and all host packages on each stack. For DCN deployments, you must upgrade the central stack last. For multi-cell deployments, you must upgrade the control stack last:
openstack overcloud upgrade run --stack <stack> --tags setup_packages,ovn --limit allovercloud --yes
$ openstack overcloud upgrade run --stack <stack> --tags setup_packages,ovn --limit allovercloud --yes
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Replace
<stack>
with the name of the stack you are upgrading.Verify that the
ovn-controller
is updated on all overcloud nodes:sudo podman ps | grep ovn_controller
$ sudo podman ps | grep ovn_controller
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Sample output
5ddc21ef9056 undercloud-0.ctlplane.redhat.local:8787/rh-osbs/rhosp17-openstack-ovn-controller:17.1_20230905.1 kolla_start 20 hours ago Up 20 hours (healthy) ovn_controller
5ddc21ef9056 undercloud-0.ctlplane.redhat.local:8787/rh-osbs/rhosp17-openstack-ovn-controller:17.1_20230905.1 kolla_start 20 hours ago Up 20 hours (healthy) ovn_controller
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Upgrade the service containers and update the host packages on each stack, starting with the central stack or control stack:
openstack overcloud upgrade run --stack <stack> --skip-tags ovn --limit allovercloud --yes
$ openstack overcloud upgrade run --stack <stack> --skip-tags ovn --limit allovercloud --yes
Copy to Clipboard Copied! Toggle word wrap Toggle overflow