Uploaded image for project: 'ovsdb'
  1. ovsdb
  2. OVSDB-327

QoS and Queues not removed from operational after delete when using OVS 2.5 docker image

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Done
    • unspecified
    • None
    • None
    • Operating System: All
      Platform: All

    • 5648

    Description

      Bug was observed in southbound-it. Specifically in SouthboundIT.testAddDeleteQueue and SouthboundIT.testAddDeleteQoS but also in other tests.

      Root cause is code in the execute method of OvsdbQoSRemovedCommand and OvsdbQueueRemovedCommand. The deleteQoS/Queue methods are only called if the update notification contains modifications to the OpenVSwitch table. My guess is that in 2.5 OVS optimizes the notification out for the OpenVSwitch table because although an update was sent to OVS, data was not changed.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            Unassigned Unassigned
            jhershbe Josh Hershberg
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: