Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-15457

BW limit removed from LSP when VM with vlan network is migrated

XMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • rhos-18.0.8
    • openstack-neutron-22.2.2-18.0.20250529064820.51e19bb.el9ost
    • None
    • Hide
      .QoS information for VLAN or flat network ports persists through port updates

      Any VLAN or flat network port with egress QoS policy rules (maximum and/or minimum bandwidth) stores this information in the `Logical_Switch_Port. options` dictionary. Before this update, any update on this port, from a port name change to a live migration, deleted this QoS information. With this update, the QoS information persists through port updates.
      Show
      .QoS information for VLAN or flat network ports persists through port updates Any VLAN or flat network port with egress QoS policy rules (maximum and/or minimum bandwidth) stores this information in the `Logical_Switch_Port. options` dictionary. Before this update, any update on this port, from a port name change to a live migration, deleted this QoS information. With this update, the QoS information persists through port updates.
    • Bug Fix
    • Done
    • Rejected
    • Neutron Sprint 11
    • 1
    • Important

      Bug reproduced on RHOSO 18 using either live or cold migration.

      The following WNTP tests reproduce it: test_qos_after_live_migration and test_qos_after_cold_migration
      https://opendev.org/x/whitebox-neutron-tempest-plugin/src/branch/master/whitebox_neutron_tempest_plugin/tests/scenario/test_qos.py

       

      The manual reproduction is quite simple:

      1. create a VM with a port from a VLAN tenant network
      2. add a QoS policy with BW limit to that network
      3. check on OVN NB DB that the BW limit has been applied to the VM's LSP (see example [1])
      4. migrate (either live or cold) that VM to a different compute
      5. check on OVN NB DB that the BW limit has not been changed on the VM's LSP. This currently fails because the max_rate and burst options are removed after the migration (see example [2])

       

      This is a regression because this didn't fail with previous RHOSO versions. It seems behavior has changed due to OSPRH-11045.

       

      [1] 

       

      [zuul@controller-0 ~]$ oc rsh ovsdbserver-nb-0 ovn-nbctl --no-leader get logical_switch_port 3a9223f4-397b-4919-8d00-7571c1e036f4 options
      {qos_burst="800000", qos_max_rate="1000000", requested-chassis=compute-zyei6xva-0.ctlplane.example.com} 
      

       

      [2] 

      [zuul@controller-0 ~]$ oc rsh ovsdbserver-nb-0 ovn-nbctl --no-leader get logical_switch_port 3a9223f4-397b-4919-8d00-7571c1e036f4 options
      {requested-chassis=compute-zyei6xva-1.ctlplane.example.com}

              rodolfo_alonso Rodolfo Alonso
              eolivare Eduardo Olivares Toledo
              Eduardo Olivares Toledo Eduardo Olivares Toledo
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: