Keeping Red Hat OpenStack Platform Updated

Procedure

1. Log into the director as the stack user.

2. Run dnf to upgrade the director’s main packages:

   $ sudo dnf update -y python3-tripleoclient* openstack-tripleo-common openstack-tripleo-heat-templates

   Copy to Clipboard Toggle word wrap

3. The director uses the openstack undercloud upgrade command to update the undercloud environment. Run the command:

   $ openstack undercloud upgrade

   Copy to Clipboard Toggle word wrap
4. Wait until the undercloud upgrade process completes.

5. Reboot the undercloud to update the operating system’s kernel and other system packages:

   $ sudo reboot

   Copy to Clipboard Toggle word wrap
6. Wait until the node boots.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Remove any existing images from the images directory on the stack user’s home (/home/stack/images):

   $ rm -rf ~/images/*

   Copy to Clipboard Toggle word wrap

3. Extract the archives:

   $ cd ~/images
   $ for i in /usr/share/rhosp-director-images/overcloud-full-latest-15.0.tar /usr/share/rhosp-director-images/ironic-python-agent-latest-15.0.tar; do tar -xvf $i; done
   $ cd ~

   Copy to Clipboard Toggle word wrap

4. Import the latest images into the director:

   $ openstack overcloud image upload --update-existing --image-path /home/stack/images/

   Copy to Clipboard Toggle word wrap

5. Configure your nodes to use the new images:

   $ openstack overcloud node configure $(openstack baremetal node list -c UUID -f value)

   Copy to Clipboard Toggle word wrap

6. Verify the existence of the new images:

   $ openstack image list
   $ ls -l /httpboot

   Copy to Clipboard Toggle word wrap

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the update preparation command:

   $ openstack overcloud update prepare \
       --templates \
       -r <ROLES DATA FILE> \
       -n <NETWORK DATA FILE> \
       -e <ENVIRONMENT FILE> \
       -e <ENVIRONMENT FILE> \
       ...

   Copy to Clipboard Toggle word wrap

   Include the following options relevant to your environment:

   • Custom configuration environment files (-e)
   • If using your own custom roles, include your custom roles (roles_data) file (-r)
   • If using custom networks, include your composable network (network_data) file (-n)
3. Wait until the update preparation completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the openstack overcloud external-update run command against tasks tagged with the container_image_prepare tag:

   $ openstack overcloud external-update run --tags container_image_prepare

   Copy to Clipboard Toggle word wrap

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the update command:

   $ openstack overcloud update run --nodes Controller

   Copy to Clipboard Toggle word wrap
3. Wait until the Controller node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the update command:

   $ openstack overcloud update run --nodes Compute

   Copy to Clipboard Toggle word wrap
3. Wait until the Compute node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the update command:

   $ openstack overcloud update run --nodes ComputeHCI

   Copy to Clipboard Toggle word wrap
3. Wait until the node update completes.

4. Run the Ceph Storage update command. For example:

   $ openstack overcloud ceph-upgrade run \
       --templates \
       -e <ENVIRONMENT FILE> \
       -e /home/stack/templates/overcloud_images.yaml

   Copy to Clipboard Toggle word wrap

   Include the following options relevant to your environment:

   • Custom configuration environment files (-e)
   • The environment file with your container image locations (-e). Note that the update command might display a warning about using the --container-registry-file. You can ignore this warning as this option is deprecated in favor of using -e for the container image environment file.
   • If applicable, your custom roles (roles_data) file (--roles-file)
   • If applicable, your composable network (network_data) file (--networks-file)
5. Wait until the Compute HCI node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the update command:

   $ openstack overcloud update run --nodes CephStorage

   Copy to Clipboard Toggle word wrap
3. Wait until the node update completes.

4. Run the Ceph Storage container update command:

   $ openstack overcloud external-update run --tags ceph

   Copy to Clipboard Toggle word wrap
5. Wait until the Ceph Storage container update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the openstack overcloud external-update run command against tasks tagged with the online_upgrade tag:

   $ openstack overcloud external-update run --tags online_upgrade

   Copy to Clipboard Toggle word wrap

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the update finalization command:

   $ openstack overcloud update converge \
       --templates \
       -e <ENVIRONMENT FILE> \
       -e <ENVIRONMENT FILE> \
       ...

   Copy to Clipboard Toggle word wrap

   Include the following options relevant to your environment:

   • Custom configuration environment files (-e).
   • If applicable, your custom roles (roles_data) file (--roles-file)
   • If applicable, your composable network (network_data) file (--networks-file)
3. Wait until the update finalization completes.

Procedure

1. Log in to the node that you want to reboot.

2. Optional: If the node uses Pacemaker resources, stop the cluster:

   [heat-admin@overcloud-controller-0 ~]$ sudo pcs cluster stop

   Copy to Clipboard Toggle word wrap

3. Reboot the node:

   [heat-admin@overcloud-controller-0 ~]$ sudo reboot

   Copy to Clipboard Toggle word wrap
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:

      [heat-admin@overcloud-controller-0 ~]$ sudo pcs status

      Copy to Clipboard Toggle word wrap

   2. If the node uses Systemd services, check all services are enabled:

      [heat-admin@overcloud-controller-0 ~]$ sudo systemctl status

      Copy to Clipboard Toggle word wrap

   3. If the node uses containerized services, check all containers on the node are active:

      [heat-admin@overcloud-controller-0 ~]$ sudo podman ps

      Copy to Clipboard Toggle word wrap

Procedure

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

   $ sudo podman exec -it ceph-mon-controller-0 ceph osd set noout
   $ sudo podman exec -it ceph-mon-controller-0 ceph osd set norebalance

   Copy to Clipboard Toggle word wrap
2. Select the first Ceph Storage node to reboot and log into the node.

3. Reboot the node:

   $ sudo reboot

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

5. Log in to the node and check the cluster status:

   $ sudo podman exec -it ceph-mon-controller-0 ceph status

   Copy to Clipboard Toggle word wrap

   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:

   $ sudo podman exec -it ceph-mon-controller-0 ceph osd unset noout
   $ sudo podman exec -it ceph-mon-controller-0 ceph osd unset norebalance

   Copy to Clipboard Toggle word wrap

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

   $ sudo podman exec -it ceph-mon-controller-0 ceph status

   Copy to Clipboard Toggle word wrap

Procedure

1. Log in to the undercloud as the stack user.

2. List all Compute nodes and their UUIDs:

   $ source ~/stackrc
   (undercloud) $ openstack server list --name compute

   Copy to Clipboard Toggle word wrap

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

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

   $ source ~/overcloudrc
   (overcloud) $ openstack compute service list
   (overcloud) $ openstack compute service set [hostname] nova-compute --disable

   Copy to Clipboard Toggle word wrap

4. List all instances on the Compute node:

   (overcloud) $ openstack server list --host [hostname] --all-projects

   Copy to Clipboard Toggle word wrap
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:

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

7. Wait until migration completes.

8. Confirm the migration was successful:

   (overcloud) $ openstack server list --host [hostname] --all-projects

   Copy to Clipboard Toggle word wrap
9. Continue migrating instances until none remain on the chosen Compute Node.

10. Log in to the Compute Node. Reboot the node:

    [heat-admin@overcloud-compute-0 ~]$ sudo reboot

    Copy to Clipboard Toggle word wrap
11. Wait until the node boots.

12. Enable the Compute Node again:

    $ source ~/overcloudrc
    (overcloud) $ openstack compute service set [hostname] nova-compute --enable

    Copy to Clipboard Toggle word wrap

13. Check whether the Compute node is enabled:

    (overcloud) $ openstack compute service list

    Copy to Clipboard Toggle word wrap

Procedure

1. Log in to a Ceph MON or a Controller node and identify the name of the Ceph MON container:

   $ sudo podman ps | grep -i ceph | grep -i mon
   
   45fe68d340e5  docker-registry.upshift.redhat.com/ceph/rhceph-4.0-rhel8:latest

   Copy to Clipboard Toggle word wrap

2. Set the CEPH_MON_CONTAINER variable to the name of the container:

   $ CEPH_MON_CONTAINER=ceph-mon-controller-0

   Copy to Clipboard Toggle word wrap

3. Verify that you can use the CEPH_MON_CONTAINER variable to run Ceph commands:

   $ sudo podman exec $CEPH_MON_CONTAINER ceph -s

   Copy to Clipboard Toggle word wrap

4. From the Ceph MON or Controller node, disable Ceph Storage cluster rebalancing temporarily:

   $ sudo podman exec $CEPH_MON_CONTAINER ceph osd set noout
   $ sudo podman exec $CEPH_MON_CONTAINER ceph osd set norebalance

   Copy to Clipboard Toggle word wrap
5. Log in to the undercloud as the stack user.

6. List all Compute nodes and their UUIDs:

   $ source ~/stackrc
   (undercloud) $ openstack server list --name compute

   Copy to Clipboard Toggle word wrap

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

7. From the undercloud, select a Compute node 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

8. List all instances on the Compute node:

   (overcloud) $ openstack server list --host [hostname] --all-projects

   Copy to Clipboard Toggle word wrap

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

10. Wait until the migration completes.

11. Confirm that the migration was successful:

    (overcloud) $ openstack server list --host [hostname] --all-projects

    Copy to Clipboard Toggle word wrap
12. Continue migrating instances until none remain on the chosen Compute node.

13. Log in to a Ceph MON or a Controller node and check the cluster status:

    $ sudo podman exec $CEPH_MON_CONTAINER ceph -s

    Copy to Clipboard Toggle word wrap

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

14. Reboot the Compute HCI node:

    $ sudo reboot

    Copy to Clipboard Toggle word wrap
15. Wait until the node boots.

16. Enable the Compute node again:

    $ source ~/overcloudrc
    (overcloud) $ openstack compute service set [hostname] nova-compute --enable

    Copy to Clipboard Toggle word wrap

17. Verify that the Compute node is enabled:

    (overcloud) $ openstack compute service list

    Copy to Clipboard Toggle word wrap
18. Log out of the node, reboot the next node, and check its status. Repeat this process until you have rebooted all Ceph storage nodes.

19. When complete, log in to a Ceph MON or Controller node and enable cluster rebalancing again:

    $ sudo podman exec $CEPH_MON_CONTAINER ceph osd unset noout
    $ sudo podman exec $CEPH_MON_CONTAINER ceph osd unset norebalance

    Copy to Clipboard Toggle word wrap

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

    $ sudo podman exec $CEPH_MON_CONTAINER ceph status

    Copy to Clipboard Toggle word wrap