OpenDaylight JIRA https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 [VTN-44] System test for VTN Manager fails. https://jira.opendaylight.org/browse/VTN-44 vtn <p>Continuous System Integration Test for VTN Manager features failed continuously.</p> <p><a href="https://jenkins.opendaylight.org/integration/view/CSIT%20Jobs/job/integration-master-csit-karaf-vtn-all/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/view/CSIT%20Jobs/job/integration-master-csit-karaf-vtn-all/</a></p> <p>Tests from #165 to #174 of the above Jenkins job failed.</p> <p>Sometimes it failed to forward ping packets.<br/> <a href="https://jenkins.opendaylight.org/integration/view/CSIT%20Jobs/job/integration-master-csit-karaf-vtn-all/167/robot/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/view/CSIT%20Jobs/job/integration-master-csit-karaf-vtn-all/167/robot/</a></p> <p>Other times it failed to delete a virtual tenant network.<br/> <a href="https://jenkins.opendaylight.org/integration/view/CSIT%20Jobs/job/integration-master-csit-karaf-vtn-all/174/robot/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/view/CSIT%20Jobs/job/integration-master-csit-karaf-vtn-all/174/robot/</a></p> <p>Operating System: All<br/> Platform: All</p> VTN-44 System test for VTN Manager fails. Bug Resolved Done Unassigned Hideyuki Tai Tue, 7 Oct 2014 18:12:02 +0000 Thu, 19 Oct 2017 22:33:53 +0000 Tue, 30 Jun 2015 16:30:26 +0000 unspecified VTN Manager 0 4 <p>We've analyzed the failure of build #173 of the csit-karaf-vtn-all.<br/> <a href="https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/173/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/173/</a></p> <p>The #173 succeeded to forward ping packets between h1 and h3 on a virtual bridge "vBridge1".<br/> However, it failed to forward ping packets between h2 and h4 on a virtual bridge "vBridge2".<br/> <a href="https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/173/robot/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/173/robot/</a></p> <p>We've also checked the log file of the #173.<br/> <a href="https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/173/artifact/karaf.log" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/173/artifact/karaf.log</a></p> <p>We've found out that TopologyManager received the notification of the edge addition (s3-eth2 &lt;-&gt; s1-eth2) before the notification of Node &amp; NodeConnector (s3, s3-eth2, and s1-eth2) addition so that TopologyManager ignored the edge.<br/> In such a case, dijkstra_implementation and VTN Manager are not notified of edge notification.<br/> We guess this is related to the ping failure.</p> <p>2014-10-06 08:58:02,394 | WARN | DOM-OPER-DCL-8 | TopologyManagerImpl | 359 - org.opendaylight.controller.topologymanager - 0.4.2.SNAPSHOT | Ignore edge that contains invalid node connector: (OF|3@OF|00:00:00:00:00:00:00:03-&gt;OF|2@OF|00:00:00:00:00:00:00:01)</p> <p>2014-10-06 08:58:02,398 | WARN | DOM-OPER-DCL-8 | TopologyManagerImpl | 359 - org.opendaylight.controller.topologymanager - 0.4.2.SNAPSHOT | Ignore edge that contains invalid node connector: (OF|2@OF|00:00:00:00:00:00:00:01-&gt;OF|3@OF|00:00:00:00:00:00:00:03)</p> <p>2014-10-06 08:58:02,401 | INFO | DOM-OPER-DCL-6 | VTNManagerImpl | 450 - org.opendaylight.vtn.manager.implementation - 0.2.0.SNAPSHOT | default: addNode: New node OF|00:00:00:00:00:00:00:03</p> <p>2014-10-06 08:58:02,401 | INFO | DOM-OPER-DCL-6 | VTNManagerImpl | 450 - org.opendaylight.vtn.manager.implementation - 0.2.0.SNAPSHOT | default: addPort: New port: port=OF|2@OF|00:00:00:00:00:00:00:03, prop=PortProperty<span class="error">&#91;name=s3-eth2,cost=1000,enabled&#93;</span></p> <p>2014-10-06 08:58:02,416 | INFO | DOM-OPER-DCL-6 | VTNManagerImpl | 450 - org.opendaylight.vtn.manager.implementation - 0.2.0.SNAPSHOT | default: addPort: New port: port=OF|2@OF|00:00:00:00:00:00:00:01, prop=PortProperty<span class="error">&#91;name=s1-eth2,cost=1000,enabled&#93;</span></p> <p>In this case, we think that VTN Manager would output an ERROR message saying a Path Fault occurred, and it would fail to forward ping packets between h1 and h3 as well.<br/> However, we cannot find the ERROR message saying a Path Fault, and it didn't fail to forward ping packets between h1 and h3.<br/> That's weird.</p> <p>Further investigation is required for this bug.</p> <p>I've also analyzed the failure of build #175 of the csit-karaf-vtn-all.</p> <p><a href="https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/175/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/175/</a></p> <p>On the #175, the exactly same thing happened.</p> <p>It means that TopologyManager received the notification of the edge addition (s3-eth2 &lt;-&gt; s1-eth2) before the notification of Node &amp; NodeConnector (s3, s3-eth2, and s1-eth2) addition so that TopologyManager ignored the edge.</p> <p><a href="https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/174/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/174/</a></p> <p>In the #174, the following eight tests failed.</p> <p> 1. Delete a vtn Tenant1.<br/> 2. Add a vtn Tenant1.<br/> 3. Add a vBridge vBridge1.<br/> 4. Add a interface If1.<br/> 5. Add a interface if2.<br/> 6. Add a vBridge vBridge2.<br/> 7. Add a interface If3.<br/> 8. Add a interface if4.</p> <p>The last seven tests assume that the first test (Delete a vtn Tenant1) successes and it cleans up all VTN configuration.<br/> Therefore, if the first test fails to delete the vtn, the last seven tests inevitably fail.</p> <p>Therefore, I've focused on analyzing why it was failed to delete "Tenant1".</p> <p><a href="https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/174/robot/Karaf-Vtn/VTN/Vtn%20Manager/Delete%20a%20vtn%20Tenant1/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/174/robot/Karaf-Vtn/VTN/Vtn%20Manager/Delete%20a%20vtn%20Tenant1/</a></p> <p>The test client output the following error message for the failure of the deletion of "Tenant1".</p> <p> ConnectionError: <span class="error">&#91;Errno 104&#93;</span> Connection reset by peer</p> <p>I think it means that the controller sent a RST packet to the test client.<br/> But, I don't know why it happens.<br/> I could not find any message related to this issue in the log file of the controller.<br/> <a href="https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/174/artifact/karaf.log" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/174/artifact/karaf.log</a></p> <p>The #172 also failed due to the exactly same reason.<br/> <a href="https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/172/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/172/</a><br/> The test client failed to delete a vtn named "Tenant1", and it output the following message.<br/> ConnectionError: <span class="error">&#91;Errno 104&#93;</span> Connection reset by peer<br/> <a href="https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/172/robot/Karaf-Vtn/VTN%20OF13/Vtn%20Manager/Delete%20a%20vtn%20Tenant1/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/integration/job/integration-master-csit-karaf-vtn-all/172/robot/Karaf-Vtn/VTN%20OF13/Vtn%20Manager/Delete%20a%20vtn%20Tenant1/</a></p> <p>Anyway, I think the root cause of the failure of the #174 is different from the root cause of #173.</p> <p>Hi Hideyuki,</p> <p>After trying with my local device, I do not really see any ping failure BUT I do see the problem of deleting tenant time to time.</p> <p>ConnectionError: <span class="error">&#91;Errno 104&#93;</span> Connection reset by peer</p> <p>BR/Luis</p> <p>Hi Luis,</p> <p>Thank you for sharing the observation!</p> <p>We think the <a href="https://jira.opendaylight.org/browse/CONTROLLER-927" title="The order of switch event notification is not maintained correctly." class="issue-link" data-issue-key="CONTROLLER-927"><del>CONTROLLER-927</del></a> caused the ping problem.</p> <p>&gt; ConnectionError: <span class="error">&#91;Errno 104&#93;</span> Connection reset by peer</p> <p>I'm not sure why this happened.<br/> I think it means that the controller sent a RST packet to the test client.<br/> Because, VTN Manager never send RST packets, I guess there are something wrong in other bundles.</p> <p>Is this a TCP RST being sent to a REST client?</p> <p>(In reply to Ed Warnicke from comment #6)<br/> &gt; Is this a TCP RST being sent to a REST client?</p> <p>I think so.<br/> I'm not sure which bundle makes this happen.</p> <p>I've submitted a patch for this issue into controller.git.<br/> <a href="https://git.opendaylight.org/gerrit/#/c/12876/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/12876/</a></p> <p>After starting my Karaf I see Karaf becoming very slow. The main packages installed are : odl-nsf-all, odl-openflowplugin-all, odl-adsal-compatibility-all, and odl-vtn-manager-all .</p> <p>Is there any conflict in this.</p> <p>The modules which are installed in karaf include:<br/> Name | Version | Installed | Repository | Description <br/> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------<br/> standard | 3.0.1 | x | standard-3.0.1 | Karaf standard feature <br/> config | 3.0.1 | x | standard-3.0.1 | Provide OSGi ConfigAdmin support <br/> region | 3.0.1 | x | standard-3.0.1 | Provide Region Support <br/> package | 3.0.1 | x | standard-3.0.1 | Package commands and mbeans <br/> http | 3.0.1 | x | standard-3.0.1 | Implementation of the OSGI HTTP Service <br/> war | 3.0.1 | x | standard-3.0.1 | Turn Karaf as a full WebContainer <br/> kar | 3.0.1 | x | standard-3.0.1 | Provide KAR (KARaf archive) support <br/> ssh | 3.0.1 | x | standard-3.0.1 | Provide a SSHd server on Karaf <br/> management | 3.0.1 | x | standard-3.0.1 | Provide a JMX MBeanServer and a set of MBeans in K<br/> odl-ovsdb-all | 1.0.1-Helium-SR1 | x | ovsdb-1.0.1-Helium-SR1 | OpenDaylight :: OVSDB :: all <br/> odl-ovsdb-library | 1.0.1-Helium-SR1 | x | ovsdb-1.0.1-Helium-SR1 | OVSDB :: Library <br/> odl-ovsdb-schema-openvswitch | 1.0.1-Helium-SR1 | x | ovsdb-1.0.1-Helium-SR1 | OVSDB :: Schema :: Open_vSwitch <br/> odl-ovsdb-schema-hardwarevtep | 1.0.1-Helium-SR1 | x | ovsdb-1.0.1-Helium-SR1 | OVSDB :: Schema :: hardware_vtep <br/> odl-ovsdb-plugin | 1.0.1-Helium-SR1 | x | ovsdb-1.0.1-Helium-SR1 | OpenDaylight :: OVSDB :: Plugin <br/> odl-ovsdb-northbound | 0.6.1-Helium-SR1 | x | ovsdb-1.0.1-Helium-SR1 | OpenDaylight :: OVSDB :: Northbound <br/> odl-openflowjava-protocol | 0.5.1-Helium-SR1 | x | odl-openflowjava-0.5.1-Helium-SR1 | OpenDaylight :: Openflow Java :: Protocol <br/> odl-vtn-manager-all | 0.2.1-Helium-SR1 | x | vtn-manager-0.2.1-Helium-SR1 | OpenDaylight VTN Manager All <br/> odl-vtn-manager-java-api | 0.2.1-Helium-SR1 | x | vtn-manager-0.2.1-Helium-SR1 | OpenDaylight :: VTN Manager :: Java API <br/> odl-vtn-manager-northbound | 0.2.1-Helium-SR1 | x | vtn-manager-0.2.1-Helium-SR1 | OpenDaylight :: VTN Manager :: Northbound <br/> odl-vtn-manager-neutron | 0.2.1-Helium-SR1 | x | vtn-manager-0.2.1-Helium-SR1 | OpenDaylight :: VTN Manager :: Neutron Interface <br/> odl-restconf | 1.1.1-Helium-SR1 | x | odl-controller-1.1.1-Helium-SR1 | OpenDaylight :: Restconf <br/> odl-restconf-noauth | 1.1.1-Helium-SR1 | x | odl-controller-1.1.1-Helium-SR1 | OpenDaylight :: Restconf <br/> odl-mdsal-apidocs | 1.1.1-Helium-SR1 | x | odl-controller-1.1.1-Helium-SR1 | OpenDaylight :: MDSAL :: APIDOCS <br/> odl-openflowplugin-all | 0.0.4-Helium-SR1 | x | openflowplugin-0.0.4-Helium-SR1 | OpenDaylight :: Openflow Plugin :: All <br/> odl-openflowplugin-southbound | 0.0.4-Helium-SR1 | x | openflowplugin-0.0.4-Helium-SR1 | OpenDaylight :: Openflow Plugin :: SouthBound <br/> odl-openflowplugin-flow-services | 0.0.4-Helium-SR1 | x | openflowplugin-0.0.4-Helium-SR1 | OpenDaylight :: Openflow Plugin :: Flow Services <br/> odl-openflowplugin-flow-services-rest | 0.0.4-Helium-SR1 | x | openflowplugin-0.0.4-Helium-SR1 | OpenDaylight :: Openflow Plugin :: Flow Services :<br/> odl-openflowplugin-flow-services-ui | 0.0.4-Helium-SR1 | x | openflowplugin-0.0.4-Helium-SR1 | OpenDaylight :: Openflow Plugin :: Flow Services :<br/> odl-mdsal-common | 1.1.1-Helium-SR1 | x | odl-config-0.2.6-Helium-SR1 | OpenDaylight :: Config :: All <br/> odl-config-api | 0.2.6-Helium-SR1 | x | odl-config-0.2.6-Helium-SR1 | OpenDaylight :: Config :: API <br/> odl-config-netty-config-api | 0.2.6-Helium-SR1 | x | odl-config-0.2.6-Helium-SR1 | OpenDaylight :: Config :: Netty Config API <br/> odl-config-core | 0.2.6-Helium-SR1 | x | odl-config-0.2.6-Helium-SR1 | OpenDaylight :: Config :: Core <br/> odl-config-manager | 0.2.6-Helium-SR1 | x | odl-config-0.2.6-Helium-SR1 | OpenDaylight :: Config :: Manager <br/> odl-protocol-framework | 0.5.1-Helium-SR1 | x | odl-protocol-framework-0.5.1-Helium-SR1 | OpenDaylight :: Protocol Framework <br/> odl-mdsal-broker | 1.1.1-Helium-SR1 | x | odl-mdsal-1.1.1-Helium-SR1 | OpenDaylight :: MDSAL :: Broker <br/> odl-mdsal-xsql | 1.1.1-Helium-SR1 | x | odl-mdsal-1.1.1-Helium-SR1 | <br/> odl-yangtools-models | 0.6.3-Helium-SR1 | x | odl-yangtools-0.6.3-Helium-SR1 | OpenDaylight :: Yangtools :: Models <br/> odl-yangtools-data-binding | 0.6.3-Helium-SR1 | x | odl-yangtools-0.6.3-Helium-SR1 | OpenDaylight :: Yangtools :: Data Binding <br/> odl-yangtools-binding | 0.6.3-Helium-SR1 | x | odl-yangtools-0.6.3-Helium-SR1 | OpenDaylight :: Yangtools :: Binding <br/> odl-yangtools-common | 0.6.3-Helium-SR1 | x | odl-yangtools-0.6.3-Helium-SR1 | OpenDaylight :: Yangtools :: Common <br/> odl-yangtools-binding-generator | 0.6.3-Helium-SR1 | x | odl-yangtools-0.6.3-Helium-SR1 | OpenDaylight :: Yangtools :: Binding Generator <br/> odl-flow-model | 1.1.1-Helium-SR1 | x | odl-flow-1.1.1-Helium-SR1 | OpenDaylight :: Flow :: Model <br/> odl-flow-services | 1.1.1-Helium-SR1 | x | odl-flow-1.1.1-Helium-SR1 | OpenDaylight :: Flow :: Services <br/> odl-dlux-core | 0.1.1-Helium-SR1 | x | odl-dlux-0.1.1-Helium-SR1 | <br/> odl-platformmanager | 0.0.1-SNAPSHOT | x | platformmanager-0.0.1-SNAPSHOT | OpenDaylight :: OneController :: Platform Manager <br/> odl-netconf-api | 0.2.6-Helium-SR1 | x | odl-netconf-0.2.6-Helium-SR1 | OpenDaylight :: Netconf :: API <br/> odl-netconf-mapping-api | 0.2.6-Helium-SR1 | x | odl-netconf-0.2.6-Helium-SR1 | OpenDaylight :: Netconf :: Mapping API <br/> odl-netconf-util | 0.2.6-Helium-SR1 | x | odl-netconf-0.2.6-Helium-SR1 | <br/> odl-netconf-impl | 0.2.6-Helium-SR1 | x | odl-netconf-0.2.6-Helium-SR1 | OpenDaylight :: Netconf :: Impl <br/> odl-config-netconf-connector | 0.2.6-Helium-SR1 | x | odl-netconf-0.2.6-Helium-SR1 | OpenDaylight :: Netconf :: Connector <br/> odl-netconf-netty-util | 0.2.6-Helium-SR1 | x | odl-netconf-0.2.6-Helium-SR1 | OpenDaylight :: Netconf :: Netty Util <br/> odl-netconf-monitoring | 0.2.6-Helium-SR1 | x | odl-netconf-0.2.6-Helium-SR1 | OpenDaylight :: Netconf :: Monitoring <br/> transaction | 1.0.1 | x | enterprise-3.0.1 | OSGi Transaction Manager <br/> odl-aaa-authn | 0.1.1-Helium-SR1 | x | odl-aaa-0.1.1-Helium-SR1 | OpenDaylight :: AAA :: Authentication <br/> pax-jetty | 8.1.14.v20131031 | x | org.ops4j.pax.web-3.1.0 | Provide Jetty engine support <br/> pax-http | 3.1.0 | x | org.ops4j.pax.web-3.1.0 | Implementation of the OSGI HTTP Service <br/> pax-http-whiteboard | 3.1.0 | x | org.ops4j.pax.web-3.1.0 | Provide HTTP Whiteboard pattern support <br/> pax-war | 3.1.0 | x | org.ops4j.pax.web-3.1.0 | Provide support of a full WebContainer <br/> odl-config-netty | 0.2.6-Helium-SR1 | x | odl-config-persister-0.2.6-Helium-SR1 | OpenDaylight :: Config-Netty <br/> odl-config-persister | 0.2.6-Helium-SR1 | x | odl-config-persister-0.2.6-Helium-SR1 | OpenDaylight :: Config Persister <br/> odl-config-startup | 0.2.6-Helium-SR1 | x | odl-config-persister-0.2.6-Helium-SR1 | OpenDaylight :: Config Persister:: Config Startup <br/> odl-adsal-all | 0.8.2-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight AD-SAL All Features <br/> odl-adsal-core | 0.8.2-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Core <br/> odl-adsal-networkconfiguration | 0.0.4-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Network Configuration <br/> odl-adsal-connection | 0.1.3-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Connection <br/> odl-adsal-clustering | 0.5.2-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Clustering <br/> odl-adsal-configuration | 0.4.4-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Configuration <br/> odl-adsal-thirdparty | 0.8.2-Helium-SR1 | x | adsal-0.8.2-Helium-SR1 | OpenDaylight :: AD-SAL :: Third-Party Depenencies <br/> odl-base-all | 1.4.3-Helium-SR1 | x | odl-base-1.4.3-Helium-SR1 | OpenDaylight Controller <br/> odl-base-dummy-console | 1.1.1-Helium-SR1 | x | odl-base-1.4.3-Helium-SR1 | Temporary Dummy Console <br/> odl-base-felix-dm | 3.1.0 | x | odl-base-1.4.3-Helium-SR1 | Felix Dependency Manager <br/> odl-base-aries-spi-fly | 1.0.0 | x | odl-base-1.4.3-Helium-SR1 | Aries SPI Fly <br/> odl-base-netty | 4.0.23.Final | x | odl-base-1.4.3-Helium-SR1 | <br/> odl-base-jersey | 1.17 | x | odl-base-1.4.3-Helium-SR1 | Jersey <br/> odl-base-jackson | 2.3.2 | x | odl-base-1.4.3-Helium-SR1 | Jackson JAX-RS <br/> odl-base-slf4j | 1.7.2 | x | odl-base-1.4.3-Helium-SR1 | SLF4J Logging <br/> odl-base-apache-commons | 1.4.3-Helium-SR1 | x | odl-base-1.4.3-Helium-SR1 | Apache Commons Libraries <br/> odl-base-eclipselink-persistence | 2.0.4.v201112161009 | x | odl-base-1.4.3-Helium-SR1 | EclipseLink Persistence API <br/> odl-base-gemini-web | 2.2.0.RELEASE | x | odl-base-1.4.3-Helium-SR1 | Gemini Web <br/> odl-base-tomcat | 7.0.53 | x | odl-base-1.4.3-Helium-SR1 | OpenDaylight Tomcat <br/> odl-base-spring | 3.1.3.RELEASE | x | odl-base-1.4.3-Helium-SR1 | Opendaylight Spring Support <br/> odl-base-spring-web | 3.1.3.RELEASE | x | odl-base-1.4.3-Helium-SR1 | OpenDaylight Spring Web <br/> odl-base-spring-security | 3.1.3.RELEASE | x | odl-base-1.4.3-Helium-SR1 | OpenDaylight Spring Security <br/> odl-nsf-all | 0.4.3-Helium-SR1 | x | nsf-0.4.3-Helium-SR1 | OpenDaylight :: NSF :: All Network Service Functio<br/> odl-nsf-managers | 0.4.3-Helium-SR1 | x | nsf-0.4.3-Helium-SR1 | OpenDaylight :: AD-SAL :: Network Service Function<br/> odl-adsal-northbound | 0.4.3-Helium-SR1 | x | nsf-0.4.3-Helium-SR1 | OpenDaylight :: AD-SAL :: Northbound APIs</p> <p>Patches to the Topology Manager for the bug have been merged into the master branch and the stable/helium branch of the controller.git.</p> <p><span class="error">&#91;master&#93;</span><br/> <a href="https://git.opendaylight.org/gerrit/#/c/12876/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/12876/</a></p> <p><span class="error">&#91;stable/helium&#93;</span><br/> <a href="https://git.opendaylight.org/gerrit/#/c/13920/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/13920/</a></p> <p>Recently, all CSIT jobs for VTN project works well.</p> <p><a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-cds-manager-all-master/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-cds-manager-all-master/</a><br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-cds-manager-only-master/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-cds-manager-only-master/</a><br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-cds-manager-all-stable-lithium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-cds-manager-all-stable-lithium/</a><br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-cds-manager-only-stable-lithium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-cds-manager-only-stable-lithium/</a></p> <p>I think the following patches also helped us.</p> <p><a href="https://git.opendaylight.org/gerrit/#/c/22650/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/22650/</a> (stable/lithium)<br/> <a href="https://git.opendaylight.org/gerrit/#/c/22254/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/22254/</a> (master)</p> Blocks CONTROLLER-927 Development External issue ID 2158 External issue URL Rank 0|i02t8n: