Chapter 5. Upgrading the undercloud

Procedure

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

2. Disable all default repositories, and enable the required Red Hat Enterprise Linux (RHEL) repositories:

   [stack@director ~]$ sudo subscription-manager repos --disable=*
   [stack@director ~]$ sudo subscription-manager repos \
   --enable=rhel-8-for-x86_64-baseos-aus-rpms \
   --enable=rhel-8-for-x86_64-appstream-aus-rpms \
   --enable=rhel-8-for-x86_64-highavailability-aus-rpms \
   --enable=openstack-17.1-for-rhel-8-x86_64-rpms \
   --enable=fast-datapath-for-rhel-8-x86_64-rpms

   Copy to Clipboard Toggle word wrap

3. Switch the container-tools module version to RHEL 8 on all nodes:

   [stack@director ~]$ sudo dnf -y module switch-to container-tools:rhel8

   Copy to Clipboard Toggle word wrap

4. Install the command line tools for director installation and configuration:

   [stack@director ~]$ sudo dnf install -y python3-tripleoclient

   Copy to Clipboard Toggle word wrap

Procedure

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

2. Source the stackrc undercloud credentials file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

3. Confirm that you can ping the overcloud nodes:

   $ tripleo-ansible-inventory --static-yaml-inventory ~/inventory.yaml --stack <stack> --ansible_ssh_user heat-admin
   $ ansible -i ~/inventory.yaml all -m ping

   Copy to Clipboard Toggle word wrap
   • Replace <stack> with the name of the stack.

4. Adjust the permissions of the /var/lib/mistral/.ssh directory:

   $ sudo chmod +x /var/lib/mistral/.ssh/

   Copy to Clipboard Toggle word wrap

5. Install the packages for validation:

   $ sudo dnf -y update openstack-tripleo-validations python3-validations-libs validations-common

   Copy to Clipboard Toggle word wrap

6. Copy the inventory from mistral:

   $ sudo chown stack:stack /var/lib/mistral/.ssh/tripleo-admin-rsa
   $ sudo cat /var/lib/mistral/<stack>/tripleo-ansible-inventory.yaml > inventory.yaml

   Copy to Clipboard Toggle word wrap

7. Run the validation:

   $ validation run -i inventory.yaml --group pre-upgrade

   Copy to Clipboard Toggle word wrap

8. Review the script output to determine which validations succeed and fail:

   === Running validation: "check-ftype" ===
   
   Success! The validation passed for all hosts:
   * undercloud

   Copy to Clipboard Toggle word wrap

9. Remove the inventory.yaml file:

   $ -rm inventory.yaml

   Copy to Clipboard Toggle word wrap

Procedure

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

2. Optional: Back up the 16.2 containers-prepare-parameter.yaml file:

   $ cp containers-prepare-parameter.yaml \
     containers-prepare-parameter.yaml.orig

   Copy to Clipboard Toggle word wrap

3. Generate the default container image preparation file:

   $ openstack tripleo container image prepare default \
     --local-push-destination \
     --output-env-file containers-prepare-parameter.yaml

   Copy to Clipboard Toggle word wrap

   This command includes the following additional options:

   • --local-push-destination sets the registry on the undercloud as the location for container images. This means that director pulls the necessary images from the Red Hat Container Catalog and pushes them to the registry on the undercloud. Director uses this registry as the container image source. To pull directly from the Red Hat Container Catalog, omit this option.

   • --output-env-file is an environment file name. The contents of this file include the parameters for preparing your container images. In this case, the name of the file is containers-prepare-parameter.yaml.

     Note

     You can use the same containers-prepare-parameter.yaml file to define a container image source for both the undercloud and the overcloud.

4. Modify the containers-prepare-parameter.yaml to suit your requirements. For more information about container image parameters, see Container image preparation parameters.

5. If your deployment includes Red Hat Ceph Storage, update the Red Hat Ceph Storage container image parameters in the containers-prepare-parameter.yaml file for the version of Red Hat Ceph Storage that your deployment uses:

   ceph_namespace: registry.redhat.io/rhceph
   ceph_image: <ceph_image_file>
   ceph_tag: latest
   ceph_grafana_image: <grafana_image_file>
   ceph_grafana_namespace: registry.redhat.io/rhceph
   ceph_grafana_tag: latest

   Copy to Clipboard Toggle word wrap

   • Replace <ceph_image_file> with the name of the image file for the version of Red Hat Ceph Storage that your deployment uses:

     • If you use director-deployed Red Hat Ceph Storage, replace <ceph_image_file> with rhceph-5-rhel8.
     • If you use external Red Hat Ceph Storage, replace <ceph_image_file> with the same Ceph image that your Red Hat Ceph Storage environment uses. For example, for a Red Hat Ceph Storage 6 image, use rhceph-6-rhel9.

   • Replace <grafana_image_file> with the name of the image file for the version of Red Hat Ceph Storage that your deployment uses:

     • If you use director-deployed Red Hat Ceph Storage, replace <grafana_image_file> with rhceph-5-dashboard-rhel8.
     • If you use external Red Hat Ceph Storage, replace <grafana_image_file> with the same Ceph image that your Red Hat Ceph Storage environment uses. For example, for a Red Hat Ceph Storage 6 image, use rhceph-6-dashboard-rhel9.

Procedure

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

2. Create a file called skip_rhel_release.yaml and set the SkipRhelEnforcement parameter to true:

   parameter_defaults:
     SkipRhelEnforcement: true

   Copy to Clipboard Toggle word wrap

3. Open the undercloud.conf file, and add the container_images_file parameter to the DEFAULT section in the file:

   container_images_file = /home/stack/containers-prepare-parameter.yaml

   Copy to Clipboard Toggle word wrap
   • The container_images_file parameter defines the location of the containers-prepare-parameter.yaml environment file so that director pulls container images for the undercloud from the correct location.

4. Add the custom_env_files parameter to the DEFAULT section in the undercloud.conf file. The custom_env_files parameter defines the location of the skip_rhel_release.yaml file that is required for the upgrade:

   custom_env_files = /home/stack/skip_rhel_release.yaml

   Copy to Clipboard Toggle word wrap

   • Add any additional custom environment files to the custom_env_files parameter, separated by a comma. Ensure that any existing files in the parameter are included in the list. For example:

     custom_env_files = /home/stack/custom-undercloud-params.yaml,/home/stack/skip_rhel_release.yaml

     Copy to Clipboard Toggle word wrap
5. Check all other parameters in the file for any changes.
6. Save the file.

Procedure

1. Confirm that the tripleo_mysql.service is running:

   $ systemctl status tripleo_mysql

   Copy to Clipboard Toggle word wrap

   Sample output

   The command shows the following output if the service is not running:

   tripleo_mysql.service - mysql container
      Loaded: loaded (/etc/systemd/system/tripleo_mysql.service; enabled; vendor preset: disabled)
      Active: inactive (dead)

   Copy to Clipboard Toggle word wrap

2. If the service is not running, start the service:

   $ sudo systemctl start tripleo_mysql

   Copy to Clipboard Toggle word wrap

3. Launch the director configuration script to upgrade director:

   $ openstack undercloud upgrade

   Copy to Clipboard Toggle word wrap

   The director configuration script upgrades director packages and configures director services to match the settings in the undercloud.conf file. This script takes several minutes to complete.

   Note

   The director configuration script prompts for confirmation before proceeding. Bypass this confirmation by using the -y option:

   $ openstack undercloud upgrade -y

   Copy to Clipboard Toggle word wrap