Chapter 1. Preparing for a minor update

Procedure

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

2. Source the stackrc undercloud credentials file:

   $ source ~/stackrc

3. Edit your overcloud subscription management environment file, which is the file that contains the RhsmVars parameter. The default name for this file is usually rhsm.yml.

4. Check if your subscription management configuration includes the rhsm_release parameter. If the rhsm_release parameter is not present, add it and set it to 9.2:

   parameter_defaults:
     RhsmVars:
       …​
       rhsm_username: "myusername"
       rhsm_password: "p@55w0rd!"
       rhsm_org_id: "1234567"
       rhsm_pool_ids: "1a85f9223e3d5e43013e3d6e8ff506fd"
       rhsm_method: "portal"
       rhsm_release: "9.2"

5. Save the overcloud subscription management environment file.

6. Create a playbook that contains a task to lock the operating system version to RHEL 9.2 on all nodes:

   $ cat > ~/set_release.yaml <<'EOF'
   - hosts: all
     gather_facts: false
     tasks:
       - name: set release to 9.2
         command: subscription-manager release --set=9.2
         become: true
   EOF

7. Run the set_release.yaml playbook:

   $ ansible-playbook -i ~/overcloud-deploy/<stack>/tripleo-ansible-inventory.yaml -f 25 ~/set_release.yaml --limit <undercloud>, <Controller>, <Compute>

   • Replace <stack> with the name of your stack.
   • Use the --limit option to apply the content to all RHOSP nodes. Replace <undercloud>, <Controller>, <Compute> with the Ansible groups in your environment that contain those nodes. Do not run this playbook against Ceph Storage nodes because you might have a different subscription for these nodes.

Procedure

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

2. Source the stackrc undercloud credentials file:

   $ source ~/stackrc

3. Edit your overcloud subscription management environment file, which is the file that contains the RhsmVars parameter. The default name for this file is usually rhsm.yml.

4. Check the rhsm_repos parameter in your subscription management configuration. If the rhsm_repos parameter is using the RHOSP 17.1 repositories, change the repository to the correct versions:

   parameter_defaults:
     RhsmVars:
       rhsm_repos:
         - rhel-9-for-x86_64-baseos-eus-rpms
         - rhel-9-for-x86_64-appstream-eus-rpms
         - rhel-9-for-x86_64-highavailability-eus-rpms
         - openstack-17.1-for-rhel-9-x86_64-rpms
         - fast-datapath-for-rhel-9-x86_64-rpms

5. Save the overcloud subscription management environment file.

6. Create a playbook that contains a task to set the repositories to RHOSP 17.1 on all nodes:

   $ cat > ~/update_rhosp_repos.yaml <<'EOF'
   - hosts: all
     gather_facts: false
     tasks:
       - name: change osp repos
         command: subscription-manager repos --enable=openstack-17.1-for-rhel-9-x86_64-rpms
         become: true
   EOF

7. Run the update_rhosp_repos.yaml playbook:

   $ ansible-playbook -i ~/overcloud-deploy/<stack>/tripleo-ansible-inventory.yaml -f 25 ~/update_rhosp_repos.yaml --limit <undercloud>,<Controller>,<Compute>

   • Replace <stack> with the name of your stack.
   • Use the --limit option to apply the content to all RHOSP nodes. Replace <undercloud>, <Controller>, and <Compute> with the Ansible groups in your environment that contain those nodes. Do not run this playbook against Ceph Storage nodes because they usually use a different subscription.

8. Create a playbook that contains a task to set the repositories to RHOSP 17.1 on all ceph storage nodes:

   $ cat > ~/update_ceph_repos.yaml <<'EOF'
   - hosts: all
     gather_facts: false
     tasks:
       - name: change ceph repos
         command: subscription-manager repos --enable=openstack-17.1-deployment-tools-for-rhel-9-x86_64-rpms
         become: true
   EOF

9. Run the update_ceph_repos.yaml playbook:

   $ ansible-playbook -i ~/overcloud-deploy/<stack>/tripleo-ansible-inventory.yaml -f 25 ~/update_ceph_repos.yaml --limit CephStorage

   Use the --limit option to apply the content to Ceph Storage nodes.

Procedure

1. Edit the container preparation file. The default name for this file is usually containers-prepare-parameter.yaml.

2. Ensure that the tag parameter is set to 17.1 for each rule set:

   parameter_defaults:
     ContainerImagePrepare:
     - push_destination: true
       set:
         ...
         tag: '17.1'
       tag_from_label: '{version}-{release}'

   Note

   If you do not want to use a specific tag for the update, such as 17.1 or 17.1.1, remove the tag key-value pair and specify tag_from_label only. This uses the installed Red Hat OpenStack Platform version to determine the value for the tag to use as part of the update process.

3. Save this file.

Procedure

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

2. Source the stackrc undercloud credentials file:

   $ source ~/stackrc

3. Log in to a Controller node and run the Pacemaker command to disable fencing:

   $ ssh tripleo-admin@<controller_ip> "sudo pcs property set stonith-enabled=false"

   • Replace <controller_ip> with the IP address of a Controller node. You can find the IP addresses of your Controller nodes with the metalsmith list command.
4. In the fencing.yaml environment file, set the EnableFencing parameter to false to ensure that fencing stays disabled during the update process.