Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 10. 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 standalone Ceph MON nodes
  4. Reboot Ceph Storage nodes
  5. Reboot Compute nodes
  6. Reboot object Storage nodes

10.1. Rebooting the Director
링크 복사

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. When the node boots, 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

10.2. Rebooting Controller Nodes
링크 복사

To reboot the Controller nodes, follow this process:

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

    $ sudo pcs cluster stop
    Copy to Clipboard Toggle word wrap

  2. Reboot the cluster: 

    $ 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: 

    $ sudo pcs cluster start
    Copy to Clipboard Toggle word wrap

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

    $ 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.

  6. Check all systemd services on the Controller Node are active: 

    $ sudo systemctl list-units "openstack*" "neutron*" "openvswitch*"
    Copy to Clipboard Toggle word wrap
  7. Log out of the node, select the next Controller Node to reboot, and repeat this procedure until you have rebooted all Controller Nodes.

10.3. Rebooting standalone Ceph MON nodes
링크 복사

To reboot the Ceph MON nodes, follow this process:

  1. Log into a Ceph MON node.

  2. Reboot the node: 

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

Repeat these steps for each MON node in the cluster.

10.4. Rebooting Ceph Storage Nodes
링크 복사

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

10.5. Rebooting Compute Nodes
링크 복사

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: 

$ nova list | grep "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
$ openstack compute service list
$ openstack compute service set [hostname] nova-compute --disable
    Copy to Clipboard Toggle word wrap

  2. List all instances on the Compute node: 

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

  3. Migrate each instance from the disabled host. Use one of the following commands:

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

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

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

      $ nova live-migration [instance-id]
      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 instance has migrated from the Compute node: 

    $ openstack server list --host [hostname] --all-projects
    Copy to Clipboard Toggle word wrap
  6. Repeat this step until you have migrated all instances from the Compute Node.
Important

For full instructions on configuring and migrating instances, see Chapter 8, Migrating Virtual Machines Between Compute Nodes.

Reboot the Compute node using the following process

  1. Log into the Compute Node and reboot it: 

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

  3. Enable the Compute Node again: 

    $ source ~/overcloudrc
$ openstack compute service set [hostname] nova-compute --enable
    Copy to Clipboard Toggle word wrap
  4. Select the next node to reboot.

10.6. Rebooting Object Storage Nodes
링크 복사

To reboot the Object Storage nodes, follow this process:

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

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

  3. Log into the node and check the status: 

    $ sudo systemctl list-units "openstack-swift*"
    Copy to Clipboard Toggle word wrap
  4. Log out of the node and repeat this process on the next Object Storage node.
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat