Chapter 4. Rebooting the overcloud After you perform a minor Red Hat OpenStack Platform (RHOSP) update to the latest 17.1 version, reboot your overcloud. The reboot refreshes the nodes with any associated kernel, system-level, and container component updates. These updates provide performance and security benefits. Plan downtime to perform the reboot procedures. Use the following guidance to understand how to reboot different node types: If you reboot all nodes in one role, reboot each node individually. If you reboot all nodes in a role simultaneously, service downtime can occur during the reboot operation. Complete the reboot procedures on the nodes in the following order: Section 4.1, "Rebooting Controller and composable nodes" Section 4.2, "Rebooting a Ceph Storage (OSD) cluster" Section 4.3, "Rebooting Compute nodes" 4.1. Rebooting Controller and composable nodes Reboot Controller nodes and standalone nodes based on composable roles, and exclude Compute nodes and Ceph Storage nodes. Procedure Log in to the node that you want to reboot. Optional: If the node uses Pacemaker resources, stop the cluster: [tripleo-admin@overcloud-controller-0 ~]USD sudo pcs cluster stop Reboot the node: [tripleo-admin@overcloud-controller-0 ~]USD sudo reboot Wait until the node boots. Verification Verify that the services are enabled. If the node uses Pacemaker services, check that the node has rejoined the cluster: [tripleo-admin@overcloud-controller-0 ~]USD sudo pcs status If the node uses Systemd services, check that all services are enabled: [tripleo-admin@overcloud-controller-0 ~]USD sudo systemctl status If the node uses containerized services, check that all containers on the node are active: [tripleo-admin@overcloud-controller-0 ~]USD sudo podman ps 4.2. Rebooting a Ceph Storage (OSD) cluster Complete the following steps to reboot a cluster of Ceph Storage (OSD) nodes. Prerequisites On a Ceph Monitor or Controller node that is running the ceph-mon service, check that the Red Hat Ceph Storage cluster status is healthy and the pg status is active+clean : USD sudo cephadm -- shell ceph status If the Ceph cluster is healthy, it returns a status of HEALTH_OK . If the Ceph cluster status is unhealthy, it returns a status of HEALTH_WARN or HEALTH_ERR . For troubleshooting guidance, see the Red Hat Ceph Storage 5 Troubleshooting Guide or the Red Hat Ceph Storage 6 Troubleshooting Guide . Procedure Log in to a Ceph Monitor or Controller node that is running the ceph-mon service, and disable Ceph Storage cluster rebalancing temporarily: USD sudo cephadm shell -- ceph osd set noout USD sudo cephadm shell -- ceph osd set norebalance Note If you have a multistack or distributed compute node (DCN) architecture, you must specify the Ceph cluster name when you set the noout and norebalance flags. For example: sudo cephadm shell -c /etc/ceph/<cluster>.conf -k /etc/ceph/<cluster>.client.keyring . Select the first Ceph Storage node that you want to reboot and log in to the node. Reboot the node: Wait until the node boots. Log in to the node and check the Ceph cluster status: USD sudo cephadm -- shell ceph status Check that the pgmap reports all pgs as normal ( active+clean ). Log out of the node, reboot the node, and check its status. Repeat this process until you have rebooted all Ceph Storage nodes. When complete, log in to a Ceph Monitor or Controller node that is running the ceph-mon service and enable Ceph cluster rebalancing: USD sudo cephadm shell -- ceph osd unset noout USD sudo cephadm shell -- ceph osd unset norebalance Note If you have a multistack or distributed compute node (DCN) architecture, you must specify the Ceph cluster name when you unset the noout and norebalance flags. For example: sudo cephadm shell -c /etc/ceph/<cluster>.conf -k /etc/ceph/<cluster>.client.keyring Perform a final status check to verify that the cluster reports HEALTH_OK : USD sudo cephadm shell ceph status 4.3. Rebooting Compute nodes To ensure minimal downtime of instances in your Red Hat OpenStack Platform environment, the Migrating instances workflow outlines the steps you must complete to migrate instances from the Compute node that you want to reboot. Migrating instances workflow Decide whether to migrate instances to another Compute node before rebooting the node. Select and disable the Compute node that you want to reboot so that it does not provision new instances. Migrate the instances to another Compute node. Reboot the empty Compute node. Enable the empty Compute node. Prerequisites Before you reboot the Compute node, you must decide whether to migrate instances to another Compute node while the node is rebooting. Review the list of migration constraints that you might encounter when you migrate virtual machine instances between Compute nodes. For more information, see Migration constraints in Configuring the Compute service for instance creation . Note If you have a Multi-RHEL environment, and you want to migrate virtual machines from a Compute node that is running RHEL 9.2 to a Compute node that is running RHEL 8.4, only cold migration is supported. For more information about cold migration, see Cold migrating an instance in Configuring the Compute service for instance creation . If you cannot migrate the instances, you can set the following core template parameters to control the state of the instances after the Compute node reboots: NovaResumeGuestsStateOnHostBoot Determines whether to return instances to the same state on the Compute node after reboot. When set to False , the instances remain down and you must start them manually. The default value is False . NovaResumeGuestsShutdownTimeout Number of seconds to wait for an instance to shut down before rebooting. It is not recommended to set this value to 0 . The default value is 300 . For more information about overcloud parameters and their usage, see Overcloud parameters . Procedure Log in to the undercloud as the stack user. Retrieve a list of your Compute nodes to identify the host name of the node that you want to reboot: Identify the host name of the Compute node that you want to reboot. Disable the Compute service on the Compute node that you want to reboot: Replace <hostname> with the host name of your Compute node. List all instances on the Compute node: (overcloud)USD openstack server list --host <hostname> --all-projects Optional: To migrate the instances to another Compute node, complete the following steps: If you decide to migrate the instances to another Compute node, use one of the following commands: To migrate the instance to a different host, run the following command: (overcloud) USD openstack server migrate <instance_id> --live <target_host> --wait Replace <instance_id> with your instance ID. Replace <target_host> with the host that you are migrating the instance to. Let nova-scheduler automatically select the target host: (overcloud) USD nova live-migration <instance_id> Live migrate all instances at once: USD nova host-evacuate-live <hostname> Note The nova command might cause some deprecation warnings, which are safe to ignore. Wait until migration completes. Confirm that the migration was successful: (overcloud) USD openstack server list --host <hostname> --all-projects Continue to migrate instances until none remain on the Compute node. Log in to the Compute node and reboot the node: [tripleo-admin@overcloud-compute-0 ~]USD sudo reboot Wait until the node boots. Re-enable the Compute node: USD source ~/overcloudrc (overcloud) USD openstack compute service set <hostname> nova-compute --enable Check that the Compute node is enabled: (overcloud) USD openstack compute service list 4.4. Validating RHOSP after the overcloud update After you update your Red Hat OpenStack Platform (RHOSP) environment, validate your overcloud with the tripleo-validations playbooks. For more information about validations, see Using the validation framework in Installing and managing Red Hat OpenStack Platform with director . Procedure Log in to the undercloud host as the stack user. Source the stackrc undercloud credentials file: Run the validation: Replace <stack> with the name of the stack. Verification To view the results of the validation report, see Viewing validation history in Installing and managing Red Hat OpenStack Platform with director . Note If a host is not found when you run a validation, the command reports the status as SKIPPED . A status of SKIPPED means that the validation is not executed, which is expected. Additionally, if a validation's pass criteria is not met, the command reports the status as FAILED . A FAILED validation does not prevent you from using your updated RHOSP environment. However, a FAILED validation can indicate an issue with your environment.

Commands:
[tripleo-admin@overcloud-controller-0 ~]USD sudo pcs cluster stop
[tripleo-admin@overcloud-controller-0 ~]USD sudo reboot
[tripleo-admin@overcloud-controller-0 ~]USD sudo pcs status
[tripleo-admin@overcloud-controller-0 ~]USD sudo systemctl status
[tripleo-admin@overcloud-controller-0 ~]USD sudo podman ps
sudo cephadm -- shell ceph status
sudo cephadm shell -- ceph osd set noout sudo cephadm shell -- ceph osd set norebalance
sudo reboot
sudo cephadm -- shell ceph status
sudo cephadm shell -- ceph osd unset noout sudo cephadm shell -- ceph osd unset norebalance
sudo cephadm shell ceph status
(undercloud)USD source ~/overcloudrc (overcloud)USD openstack compute service list
(overcloud)USD openstack compute service list (overcloud)USD openstack compute service set <hostname> nova-compute --disable
(overcloud)USD openstack server list --host <hostname> --all-projects
(overcloud) USD openstack server migrate <instance_id> --live <target_host> --wait
(overcloud) USD nova live-migration <instance_id>
nova host-evacuate-live <hostname>
(overcloud) USD openstack server list --host <hostname> --all-projects
[tripleo-admin@overcloud-compute-0 ~]USD sudo reboot
source ~/overcloudrc (overcloud) USD openstack compute service set <hostname> nova-compute --enable
(overcloud) USD openstack compute service list
source ~/stackrc
validation run -i ~/overcloud-deploy/<stack>/config-download/<stack>/tripleo-ansible-inventory.yaml --group post-update