https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OVSDB-327 ovsdb <p>Bug was observed in southbound-it. Specifically in SouthboundIT.testAddDeleteQueue and SouthboundIT.testAddDeleteQoS but also in other tests. </p> <p>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.</p> <p>Operating System: All<br/> Platform: All</p> OVSDB-327

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

Bug Resolved Done Unassigned Josh Hershberg Mon, 4 Apr 2016 08:32:21 +0000 Tue, 29 May 2018 14:58:55 +0000 Tue, 5 Apr 2016 06:15:45 +0000 unspecified Southbound.Open_vSwitch 0 3 <p>Patch is on it's way in</p> <p>Changing the logic to no longer depend on there also being changes to the OpenVSwitch table solves this issue. </p> <p>However, I am not sure if the issue is caused by version differences in OVS or because the specific instance of 2.1 (running on the "davetocker" docker) has a bunch of the optional fields of OpenVSwitch table set, e.g., system_type, that are not set on the 2.5 instance. Not sure if it makes too much of a practical difference either way but thought it worth documenting.</p> <p>I wonder if this is related to this: <br/> <a href="http://openvswitch.org/pipermail/git/2015-September/007475.html" class="external-link" target="_blank" rel="nofollow noopener">http://openvswitch.org/pipermail/git/2015-September/007475.html</a></p> Development External issue ID 5648 External issue URL Issue Type Rank 0|i0221r: