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/GENIUS-204 genius <p>TEP is part of two zones i.e. old transport zone and new transport zone when zone is removed after del-manager.</p> <p>Ideally, it should get removed from old TZ when manager is connected back and new TZ is added from NB.</p> <p>Steps:<br/> 1. Make sure setup is up with TZB transport-zone and tunnels <br/> 2. now execute "ovs-vsctl del-manager" in any of the ovs.<br/> 3. remove transport zone TZB from ovsdb and create new TZC<br/> ovs-vsctl remove O . external_ids transport-zone<br/> ovs-vsctl set O . external_ids:transport-zone=TZC<br/> 4. connect back manager to ODL.<br/> sudo ovs-vsctl set-manager tcp:192.168.40.28:6640<br/> 5. check /restconf/operational/itm:not-hosted-transport-zones/ and create a TZC from NB<br/> curl -X POST -H "Content-Type:application/json" -d @itm_tzc <a href="http://localhost:8181/restconf/config/itm:transport-zones/" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/restconf/config/itm:transport-zones</a></p> GENIUS-204

TEP is part of old and new TZ when tz is updated after del-manager

Bug Medium In Review Unresolved Tarun Thakur Tarun Thakur Mon, 6 Aug 2018 09:34:51 +0000 Mon, 6 Aug 2018 09:55:19 +0000 ITM 0 2 0 minutes 1 day <ul> <li>Fail scenario</li> </ul> <ol> <li>TZB was present and TEPs were part of it.</li> <li>ovsdb connection is removed by running delete-manager command on switch</li> <li>Change transport-zone of TEPs from TZB to TZC</li> <li>ovsdb connection is set again by running set-manager command on switch</li> <li>TEPs go under teps-not-hosted since TZC is not yet present. It is noted here that TEPs are still part of TZB in ITM config DS.</li> <li>TZC is created from northbound</li> <li>TEPs are moved from teps-not-hosted to TZC.</li> <li>In the end, TEPs are part of TZB and TZC both. This is issue.</li> </ol> <ul> <li>Fix provided</li> </ul> <p>When TEPs add notification come again with updated TZC, then check if same TEP (key: dpid) is already present in any other TZ. If present, then remove TEP from old TZ and then add TEP into newly configured TZ.</p> <p>Tarun, let us close the TR, once the patches are merged</p> <p>Ok, understood. Thanks for updating the bug.</p> Development Rank 0|i03hnz: