Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 11. Rebooting Nodes

Some situations require a reboot of nodes in the undercloud and overcloud. The following procedures show 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. This helps retain services for that role during the reboot.
  • If rebooting all nodes in your OpenStack Platform environment, use the following list to guide the reboot order:

Recommended Node Reboot Order

  1. Reboot the director
  2. Reboot Controller nodes
  3. Reboot Ceph Storage nodes
  4. Reboot Compute nodes
  5. Reboot object Storage nodes

11.1. Rebooting the Director
Link kopieren

To reboot the director node, follow this process:

  1. Reboot the node: 

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

  3. Check the status of all services: 

    $ sudo systemctl list-units "openstack*" "neutron*" "openvswitch*"
    Copy to Clipboard Toggle word wrap
    Note

    It might take approximately 10 minutes for the openstack-nova-compute to become active after a reboot.

  4. Verify the existence of your overcloud and its nodes: 

    $ source ~/stackrc
$ openstack server list
$ openstack baremetal node list
$ openstack stack list
    Copy to Clipboard Toggle word wrap

11.2. Rebooting Controller Nodes
Link kopieren

To reboot the Controller nodes, follow this process:

  1. Select a node to reboot. Log into it and stop the cluster before rebooting: 

    [heat-admin@overcloud-controller-0 ~]$ sudo pcs cluster stop
    Copy to Clipboard Toggle word wrap

  2. Reboot the cluster: 

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

    The remaining Controller Nodes in the cluster retain the high availability services during the reboot.

  3. Wait until the node boots.

  4. Re-enable the cluster for the node: 

    [heat-admin@overcloud-controller-0 ~]$ sudo pcs cluster start
    Copy to Clipboard Toggle word wrap

  5. Log into the node and check the cluster status: 

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

    The node rejoins the cluster.

Note

If any services fail after the reboot, run sudo pcs resource cleanup, which cleans the errors and sets the state of each resource to Started. If any errors persist, contact Red Hat and request guidance and assistance.

  1. Check all containers on the Controller Node are active: 

    [heat-admin@overcloud-controller-0 ~]$ sudo docker ps
    Copy to Clipboard Toggle word wrap
  2. Log out of the node, select the next Controller Node to reboot, and repeat this procedure until you have rebooted all Controller Nodes.

11.3. Rebooting Ceph Storage Nodes
Link kopieren

To reboot the Ceph Storage nodes, follow this process:

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

    $ sudo ceph osd set noout
$ sudo ceph osd set norebalance
    Copy to Clipboard Toggle word wrap
  2. Select the first Ceph Storage node to reboot and log into it.

  3. Reboot the node: 

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

  5. Log into the node and check the cluster status: 

    $ sudo ceph -s
    Copy to Clipboard Toggle word wrap

    Check that 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: 

    $ sudo ceph osd unset noout
$ sudo ceph osd unset norebalance
    Copy to Clipboard Toggle word wrap

  8. Perform a final status check to verify the cluster reports HEALTH_OK: 

    $ sudo ceph status
    Copy to Clipboard Toggle word wrap

11.4. Rebooting Compute Nodes
Link kopieren

Reboot each Compute node individually and ensure zero downtime of instances in your OpenStack Platform environment. This involves the following workflow:

  1. Select a Compute node to reboot
  2. Migrate its instances to another Compute node
  3. Reboot the empty Compute node

List all Compute nodes and their UUIDs: 

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

Select a Compute node to reboot and first migrate its instances using the following process:

  1. From the undercloud, select a Compute Node to reboot and disable it: 

    $ source ~/overcloudrc
(overcloud) $ openstack compute service list
(overcloud) $ openstack compute service set [hostname] nova-compute --disable
    Copy to Clipboard Toggle word wrap

  2. List all instances on the Compute node: 

    (overcloud) $ openstack server list --host [hostname] --all-projects
    Copy to Clipboard Toggle word wrap

  3. Use one of the following commands to migrate your instances:

    1. Migrate the instance to a specific host of your choice: 

      (overcloud) $ openstack server migrate [instance-id] --live [target-host]--wait
      Copy to Clipboard Toggle word wrap

    2. Let nova-scheduler automatically select the target host: 

      (overcloud) $ nova live-migration [instance-id]
      Copy to Clipboard Toggle word wrap

    3. Live migrate all instances at once: 

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

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

  4. Wait until migration completes.

  5. Confirm the migration was successful: 

    (overcloud) $ openstack server list --host [hostname] --all-projects
    Copy to Clipboard Toggle word wrap
  6. Continue migrating instances until none remain on the chosen Compute Node.
Important

For full instructions on configuring and migrating instances, see Section 9.10, “Migrating VMs from an Overcloud Compute Node”.

Reboot the Compute node using the following process

  1. Log into the Compute Node and reboot it: 

    [heat-admin@overcloud-compute-0 ~]$ sudo reboot
    Copy to Clipboard Toggle word wrap
  2. Wait until the node boots.

  3. Enable the Compute Node again: 

    $ source ~/overcloudrc
(overcloud) $ openstack compute service set [hostname] nova-compute --enable
    Copy to Clipboard Toggle word wrap

  4. Check whether the Compute node is enabled: 

    (overcloud) $ openstack compute service list
    Copy to Clipboard Toggle word wrap

11.5. Rebooting Object Storage Nodes
Link kopieren

To reboot the Object Storage nodes, follow this process:

  1. Select a Object Storage node to reboot. Log into it and reboot it: 

    [heat-admin@overcloud-objectstorage-0 ~]$ sudo reboot
    Copy to Clipboard Toggle word wrap
  2. Wait until the node boots.

  3. Log into the node and check the status of the containers: 

    [heat-admin@overcloud-objectstorage-0 ~]$ sudo docker ps
    Copy to Clipboard Toggle word wrap
  4. Log out of the node and repeat this process on the next Object Storage node.
Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat