ovs-vswitchd fails to start with DPDK Open vSwitch 2.9 in Red Hat OpenStack Platform 10

Resolution

In order to deploy with Open vSwitch 2.9, the ovs-vswitchd service file workarounds must be removed.

• These are usually located in first-boot.yaml and were required in older versions of Open vSwitch.
• Note that older versions of the OSP 10 minor upgrade guide also instructed users to add the same changes to their post-install.yaml.
  Advice: Run an egrep in your template Directory and search for RuntimeDirectoryMode|ovs-vswitchd.service:

    cd /home/stack/templates
    egrep  `RuntimeDirectoryMode|ovs-vswitchd.service` -R

• Note that the modifications to the tuned service files are still mandatory: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/upgrading_red_hat_openstack_platform/index#ap-rhosp10-ovs-2-9-update-post-install Otherwise, one may run into: https://access.redhat.com/solutions/3552051

In the example below the set_ovs_config OS::Heat::SoftwareConfig has the code that should be removed from first-boot.yaml. Modifications to post-install.yaml would be similar:

set_ovs_config:
    type: OS::Heat::SoftwareConfig
    properties:
      config:
        str_replace:
          template: |
            #!/bin/bash
            FORMAT=$COMPUTE_HOSTNAME_FORMAT
            if [[ -z $FORMAT ]] ; then
              FORMAT="compute" ;
            else
              # Assumption: only %index% and %stackname% are the variables in Host name format
              FORMAT=$(echo $FORMAT | sed  's/\%index\%//g' | sed 's/\%stackname\%//g') ;
            fi
            if [[ $(hostname) == *$FORMAT* ]] ; then
              if [ -f /usr/lib/systemd/system/openvswitch-nonetwork.service ]; then
                ovs_service_path="/usr/lib/systemd/system/openvswitch-nonetwork.service"
              elif [ -f /usr/lib/systemd/system/ovs-vswitchd.service ]; then
                ovs_service_path="/usr/lib/systemd/system/ovs-vswitchd.service"
              fi
              grep -q "RuntimeDirectoryMode=.*" $ovs_service_path
              if [ "$?" -eq 0 ]; then
                sed -i 's/RuntimeDirectoryMode=.*/RuntimeDirectoryMode=0775/' $ovs_service_path
              else
                echo "RuntimeDirectoryMode=0775" >> $ovs_service_path
              fi
              grep -Fxq "Group=qemu" $ovs_service_path
              if [ ! "$?" -eq 0 ]; then
                echo "Group=qemu" >> $ovs_service_path
              fi
              grep -Fxq "UMask=0002" $ovs_service_path
              if [ ! "$?" -eq 0 ]; then
                echo "UMask=0002" >> $ovs_service_path
              fi
              ovs_ctl_path='/usr/share/openvswitch/scripts/ovs-ctl'
              grep -q "umask 0002 \&\& start_daemon \"\$OVS_VSWITCHD_PRIORITY\"" $ovs_ctl_path
              if [ ! "$?" -eq 0 ]; then
                sed -i 's/start_daemon \"\$OVS_VSWITCHD_PRIORITY.*/umask 0002 \&\& start_daemon \"$OVS_VSWITCHD_PRIORITY\"             \"$OVS_VSWITCHD_WRAPPER\" \"$@\"/' $ovs_ctl_path
              fi
            fi
          params:
            $COMPUTE_HOSTNAME_FORMAT: {get_param: ComputeHostnameFormat}

Note: There are other changes required for OVS 2.9. See secton 2.1.2. NFV Pre-Configuration of the OSP 10 Upgrade guide for new template parameters.

Also, if performing an overcloud update then migration of virtual machines using DPDK is required. See section 2.3.2. NFV Post-Configuration of the upgrade guide.