Chapter 14. Rebooting nodes


You may need to reboot the nodes in the undercloud and overcloud. Use the following procedures to understand how to reboot different node types. Be aware of the following notes:

  • If rebooting all nodes in one role, it is advisable to reboot each node individually. If you reboot all nodes in a role simultaneously, you might encounter service downtime during the reboot operation.
  • If rebooting all nodes in your OpenStack Platform environment, reboot the nodes in the following sequential order:

Recommended Node Reboot Order

  1. Reboot the undercloud node
  2. Reboot Controller and other composable nodes
  3. Reboot standalone Ceph MON nodes
  4. Reboot Ceph Storage nodes
  5. Reboot Compute nodes

14.1. Rebooting the undercloud node

Complete the following steps to reboot the undercloud node.

Procedure

  1. Log into the undercloud as the stack user.
  2. Reboot the undercloud:

    Copy to Clipboard Toggle word wrap
    $ sudo reboot
  3. Wait until the node boots.

14.2. Rebooting Controller and composable nodes

Complete the following steps to reboot controller nodes and standalone nodes based on composable roles, excluding Compute nodes and Ceph Storage nodes.

Procedure

  1. Log in to the node that you want to reboot.
  2. Optional: If the node uses Pacemaker resources, stop the cluster:

    Copy to Clipboard Toggle word wrap
    [heat-admin@overcloud-controller-0 ~]$ sudo pcs cluster stop
  3. Reboot the node:

    Copy to Clipboard Toggle word wrap
    [heat-admin@overcloud-controller-0 ~]$ sudo reboot
  4. Wait until the node boots.
  5. Check the services. For example:

    1. If the node uses Pacemaker services, check the node has rejoined the cluster:

      Copy to Clipboard Toggle word wrap
      [heat-admin@overcloud-controller-0 ~]$ sudo pcs status
    2. If the node uses Systemd services, check all services are enabled:

      Copy to Clipboard Toggle word wrap
      [heat-admin@overcloud-controller-0 ~]$ sudo systemctl status
    3. If the node uses containerized services, check all containers on the node are active:

      Copy to Clipboard Toggle word wrap
      [heat-admin@overcloud-controller-0 ~]$ sudo podman ps

14.3. Rebooting standalone Ceph MON nodes

Complete the following steps to reboot standalone Ceph MON nodes.

Procedure

  1. Log into a Ceph MON node.
  2. Reboot the node:

    Copy to Clipboard Toggle word wrap
    $ sudo reboot
  3. Wait until the node boots and rejoins the MON cluster.

Repeat these steps for each MON node in the cluster.

14.4. Rebooting a Ceph Storage (OSD) cluster

Complete the following steps to reboot a cluster of Ceph Storage (OSD) nodes.

Procedure

  1. Log in to a Ceph MON or Controller node and disable Ceph Storage cluster rebalancing temporarily:

    Copy to Clipboard Toggle word wrap
    $ sudo podman exec -it ceph-mon-controller-0 ceph osd set noout
    $ sudo podman exec -it ceph-mon-controller-0 ceph osd set norebalance
  2. Select the first Ceph Storage node to reboot and log into the node.
  3. Reboot the node:

    Copy to Clipboard Toggle word wrap
    $ sudo reboot
  4. Wait until the node boots.
  5. Log in to the node and check the cluster status:

    Copy to Clipboard Toggle word wrap
    $ sudo podman exec -it ceph-mon-controller-0 ceph status

    Check the pgmap reports all pgs as normal (active+clean).

  6. Log out of the node, reboot the next node, and check its status. Repeat this process until you have rebooted all Ceph storage nodes.
  7. When complete, log into a Ceph MON or Controller node and enable cluster rebalancing again:

    Copy to Clipboard Toggle word wrap
    $ sudo podman exec -it ceph-mon-controller-0 ceph osd unset noout
    $ sudo podman exec -it ceph-mon-controller-0 ceph osd unset norebalance
  8. Perform a final status check to verify the cluster reports HEALTH_OK:

    Copy to Clipboard Toggle word wrap
    $ sudo podman exec -it ceph-mon-controller-0 ceph status

14.5. Rebooting Compute nodes

Complete the following steps to reboot Compute nodes. To ensure minimal downtime of instances in your OpenStack Platform environment, this procedure also includes instructions about migrating instances from the Compute node you want to reboot. This involves the following workflow:

  • Decide whether to migrate instances to another Compute node before rebooting the node
  • Select and disable the Compute node 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.

If for some reason you cannot or do not want to 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 will remain down and you must start them manually. 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. Default value is: 300

For general information about overcloud parameters and their usage, see Overcloud Parameters.

Procedure

  1. Log in to the undercloud as the stack user.
  2. List all Compute nodes and their UUIDs:

    Copy to Clipboard Toggle word wrap
    $ source ~/stackrc
    (undercloud) $ openstack server list --name compute

    Identify the UUID of the Compute node you want to reboot.

  3. From the undercloud, select a Compute Node. Disable the node:

    Copy to Clipboard Toggle word wrap
    $ source ~/overcloudrc
    (overcloud) $ openstack compute service list
    (overcloud) $ openstack compute service set [hostname] nova-compute --disable
  4. List all instances on the Compute node:

    Copy to Clipboard Toggle word wrap
    (overcloud) $ openstack server list --host [hostname] --all-projects
  5. If you decided not to migrate instances, skip to this step.
  6. If you decided to migrate the instances to another Compute node, use one of the following commands:

    1. Migrate the instance to a different host:

      Copy to Clipboard Toggle word wrap
      (overcloud) $ openstack server migrate [instance-id] --live [target-host]--wait
    2. Let nova-scheduler automatically select the target host:

      Copy to Clipboard Toggle word wrap
      (overcloud) $ nova live-migration [instance-id]
    3. Live migrate all instances at once:

      Copy to Clipboard Toggle word wrap
      $ nova host-evacuate-live [hostname]
      Note

      The nova command might cause some deprecation warnings, which are safe to ignore.

  7. Wait until migration completes.
  8. Confirm the migration was successful:

    Copy to Clipboard Toggle word wrap
    (overcloud) $ openstack server list --host [hostname] --all-projects
  9. Continue migrating instances until none remain on the chosen Compute Node.
  10. Log in to the Compute Node. Reboot the node:

    Copy to Clipboard Toggle word wrap
    [heat-admin@overcloud-compute-0 ~]$ sudo reboot
  11. Wait until the node boots.
  12. Enable the Compute Node again:

    Copy to Clipboard Toggle word wrap
    $ source ~/overcloudrc
    (overcloud) $ openstack compute service set [hostname] nova-compute --enable
  13. Check whether the Compute node is enabled:

    Copy to Clipboard Toggle word wrap
    (overcloud) $ openstack compute service list
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat, Inc.