Chapter 15. Performing post-upgrade actions

Procedure

1. Check the list of RPMs that you installed and ensure that there are no RHOSP 16.2 or legacy 17.1 images, for example, rhosp-director-images-x86_64-17.1:

   $ rpm -qa | egrep "rhosp-director-images-*-16.2|rhosp-director-images-x86_64-17.1"

   Copy to Clipboard Toggle word wrap

   If the list displays these images, remove them by running the following command:

   $ sudo dnf -y remove rhosp-director-images-*-16.2 rhosp-director-images-x86_64-17.1

   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-hardened-uefi-full.tar /usr/share/rhosp-director-images/ironic-python-agent-latest-17.1.tar; do tar -xvf $i; done
   $ cd ~

   Copy to Clipboard Toggle word wrap

4. Import the images into director:

   (undercloud) [stack@director images]$ openstack overcloud image upload --image-path /home/stack/images/ --update-existing

   Copy to Clipboard Toggle word wrap

   The command completes the following tasks:

   • Converts the image format from QCOW to RAW.
   • Provides status updates about the upload of the image.

Procedure

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

2. If your Compute nodes support simultaneous multithreading (SMT) but you created instances with the hw:cpu_thread_policy=isolated policy, you must perform one of the following options:

   • Create a new flavor that does not set the hw:cpu_thread_policy thread policy and resize the instances with that flavor:

     1. Source your overcloud authentication file:

        $ source ~/overcloudrc

        Copy to Clipboard Toggle word wrap

     2. Create a flavor with the default thread policy, prefer:

        (overcloud) $ openstack flavor create <flavor>

        Copy to Clipboard Toggle word wrap
        Note

        When you resize an instance, you must use a new flavor. You cannot reuse the current flavor. For more information, see Resizing an instance in the Creating and managing instances guide.

     3. Convert the instances to use the new flavor:

        (overcloud) $ openstack server resize --flavor <flavor> <server>
        (overcloud) $ openstack server resize confirm <server>

        Copy to Clipboard Toggle word wrap
     4. Repeat this step for all pinned instances that use the hw:cpu_thread_policy=isolated policy.

   • Migrate instances from the Compute node and disable SMT on the Compute node:

     1. Source your overcloud authentication file:

        $ source ~/overcloudrc

        Copy to Clipboard Toggle word wrap

     2. Disable the Compute node from accepting new virtual machines:

        (overcloud) $ openstack compute service list
        (overcloud) $ openstack compute service set <hostname> nova-compute --disable

        Copy to Clipboard Toggle word wrap
     3. Migrate all instances from the Compute node. For more information on instance migration, see Migrating virtual machine instances between Compute nodes.
     4. Reboot the Compute node and disable SMT in the BIOS of the Compute node.
     5. Boot the Compute node.

     6. Re-enable the Compute node:

        (overcloud) $ openstack compute service set <hostname> nova-compute --enable

        Copy to Clipboard Toggle word wrap

3. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap
4. Edit the environment file that contains the NovaVcpuPinSet parameter.

5. Migrate the CPU pinning configuration from the NovaVcpuPinSet parameter to NovaComputeCpuDedicatedSet and NovaComputeCpuSharedSet:

   • Migrate the value of NovaVcpuPinSet to NovaComputeCpuDedicatedSet for hosts that were previously used for pinned instances.
   • Migrate the value of NovaVcpuPinSet to NovaComputeCpuSharedSet for hosts that were previously used for unpinned instances.
   • If there is no value set for NovaVcpuPinSet, then all Compute node cores should be assigned to either NovaComputeCpuDedicatedSet or NovaComputeCpuSharedSet, depending on the type of instances you intend to host on the nodes.

   For example, your previous environment file might contain the following pinning configuration:

   parameter_defaults:
     ...
     NovaVcpuPinSet: 1,2,3,5,6,7
     ...

   Copy to Clipboard Toggle word wrap

   To migrate the configuration to a pinned configuration, set the NovaComputeCpuDedicatedSet parameter and unset the NovaVcpuPinSet parameter:

   parameter_defaults:
     ...
     NovaComputeCpuDedicatedSet: 1,2,3,5,6,7
     NovaVcpuPinSet: ""
     ...

   Copy to Clipboard Toggle word wrap

   To migrate the configuration to an unpinned configuration, set the NovaComputeCpuSharedSet parameter and unset the NovaVcpuPinSet parameter:

   parameter_defaults:
     ...
     NovaComputeCpuSharedSet: 1,2,3,5,6,7
     NovaVcpuPinSet: ""
     ...

   Copy to Clipboard Toggle word wrap
   Important

   Ensure the configuration of either NovaComputeCpuDedicatedSet or NovaComputeCpuSharedSet matches the configuration defined in NovaVcpuPinSet. To change the configuration for either of these, or to configure both NovaComputeCpuDedicatedSet or NovaComputeCpuSharedSet, ensure the Compute nodes with the pinning configuration are not running any instances before updating the configuration.

6. Save the file.

7. Run the deployment command to update the overcloud with the new CPU pinning parameters.

   (undercloud) $ openstack overcloud deploy \
       --stack _STACK NAME_ \
       --templates \
       ...
       -e /home/stack/templates/<compute_environment_file>.yaml
       ...

   Copy to Clipboard Toggle word wrap

Procedure

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

2. Source the stackrc file.

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

3. Log in to a Controller node as the heat-admin user:

   (undercloud)$ metalsmith list
   $ ssh heat-admin@<controller_ip>

   Copy to Clipboard Toggle word wrap

   Replace <controller_ip> with the IP address of the Controller node.

4. Retrieve the list of instances that have no machine type set:

   [heat-admin@<controller_ip> ~]$ sudo podman exec -i -u root nova_api \
     nova-manage libvirt list_unset_machine_type

   Copy to Clipboard Toggle word wrap

5. Check the NovaHWMachineType parameter in the nova-hw-machine-type-upgrade.yaml file for the default machine type for the instance host. The default value for the NovaHWMachineType parameter in RHOSP 16.2 is as follows:

   x86_64=pc-i440fx-rhel7.6.0,aarch64=virt-rhel7.6.0,ppc64=pseries-rhel7.6.0,ppc64le=pseries-rhel7.6.0

6. Update the system metadata of each instance with the default instance machine type:

   [heat-admin@<controller_ip> ~]$ sudo podman exec -i -u root nova_api \
     nova-manage libvirt update_machine_type <instance_uuid> <machine_type>

   Copy to Clipboard Toggle word wrap
   • Replace <instance_uuid> with the UUID of the instance.

   • Replace <machine_type> with the machine type to record for the instance.

     Warning

     If you set the machine type to something other than the machine type of the image on which the instance was booted, the existing instance might fail to boot.

7. Confirm that the machine type is recorded for all instances:

   [heat-admin@<controller_ip> ~]$ sudo podman exec -i -u root nova_api \
     nova-status upgrade check

   Copy to Clipboard Toggle word wrap

   This command returns a warning if an instance is found without a machine type. If you get this warning, repeat this procedure from step 4.

8. Change the default value of NovaHWMachineType in a Compute environment file to x86_64=q35 and deploy the overcloud.

Verification

1. Create an instance that has the default machine type:

   (overcloud)$ openstack server create --flavor <flavor> \
     --image <image> --network <network> \
     --wait defaultMachineTypeInstance

   Copy to Clipboard Toggle word wrap
   • Replace <flavor> with the name or ID of a flavor for the instance.
   • Replace <image> with the name or ID of an image that does not set hw_machine_type.
   • Replace <network> with the name or ID of the network to connect the instance to.

2. Verify that the instance machine type is set to the default value:

   [heat-admin@<controller_ip> ~]$ sudo podman exec -i -u root nova_api \
     nova-manage libvirt get_machine_type <instance_uuid>

   Copy to Clipboard Toggle word wrap

   Replace <instance_uuid> with the UUID of the instance.

3. Hard reboot an instance with a machine type of x86_64=pc-i440fx:

   (overcloud)$ openstack server reboot --hard <instance_uuid>

   Copy to Clipboard Toggle word wrap

   Replace <instance_uuid> with the UUID of the instance.

4. Verify that the instance machine type has not been changed:

   [heat-admin@<controller_ip> ~]$ sudo podman exec -i -u root nova_api \
     nova-manage libvirt get_machine_type <instance_uuid>

   Copy to Clipboard Toggle word wrap

   Replace <instance_uuid> with the UUID of the instance.

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. Log in to a Controller node and run the Pacemaker command to re-enable fencing:

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

   Copy to Clipboard Toggle word wrap
   • Replace <controller_ip> with the IP address of a Controller node. You can find the IP addresses of your Controller nodes with the openstack server list command.

4. If you use SBD fencing, reset the watchdog timer device interval to its original value before you disabled it:

   # pcs property set stonith-watchdog-timeout=<interval>

   Copy to Clipboard Toggle word wrap
   • Replace <interval> with the original value of the watchdog timer device, for example, 10.
5. In the fencing.yaml environment file, set the EnableFencing parameter to true.

Procedure

1. Enter the shell for the horizon container:

   $ podman exec -it horizon /bin/bash

   Copy to Clipboard Toggle word wrap

2. Navigate to the directory that contains the files to compress:

   $ cd /usr/bin/

   Copy to Clipboard Toggle word wrap

3. Run the compression:

   $ python3 manage.py compress

   Copy to Clipboard Toggle word wrap