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-317 ovsdb <p>The following are the setup details.</p> <p> ovsdb:latest stable/beryllium source (5 PM PST on 13-March-2016)</p> <p> OVS: version: 2.3.2</p> <p> Steps:</p> <p> 1. Start Karaf</p> <p> 2. Install feature: odl-ovsdb-openstack</p> <p> 3. Add ODL as OVS Manager usinf sudo ovs-vsctl set-manager tcp:ODL_IP:6640</p> <p> 4. Expectation: br-int gets creaeted, br-ex may get creaetd (if l3_fwd is enabled at ODL) and is_connected becomes true</p> <p> Actual: Only is_connected becomes true</p> <p> Observation: Exceptions in karaf.log</p> <p> 16-03-13 23:55:57,480 | ERROR | ult-dispatcher-5 | EntityOwnershipListenerActor | 165 - org.opendaylight<br/> .controller.sal-distributed-datastore - 1.3.1.SNAPSHOT | Error notifying listener org.opendaylight.ovsdb.south<br/> bound.OvsdbConnectionManager$OvsdbDeviceEntityOwnershipListener@735f4b78<br/> java.lang.IllegalArgumentException: Not able to create instance of class class org.opendaylight.ovsdb.lib.sche<br/> ma.GenericTableSchema using public constructor that accepts TableSchema object<br/> at org.opendaylight.ovsdb.lib.schema.DatabaseSchema.createTableSchema(DatabaseSchema.java:80)[244:org.<br/> opendaylight.ovsdb.library:1.2.2.SNAPSHOT]<br/> at org.opendaylight.ovsdb.lib.schema.DatabaseSchema.table(DatabaseSchema.java:62)[244:org.opendaylight<br/> .ovsdb.library:1.2.2.SNAPSHOT]<br/> at org.opendaylight.ovsdb.lib.schema.typed.TyperUtils.getTableSchema(TyperUtils.java:55)[244:org.opend<br/> aylight.ovsdb.library:1.2.2.SNAPSHOT]<br/> at org.opendaylight.ovsdb.lib.schema.typed.TyperUtils.extractRowUpdates(TyperUtils.java:515)[244:org.o<br/> pendaylight.ovsdb.library:1.2.2.SNAPSHOT]<br/> at org.opendaylight.ovsdb.lib.schema.typed.TyperUtils.extractRowsUpdated(TyperUtils.java:425)[244:org.<br/> opendaylight.ovsdb.library:1.2.2.SNAPSHOT]<br/> at org.opendaylight.ovsdb.southbound.transactions.md.OvsdbAutoAttachUpdateCommand.&lt;init&gt;(OvsdbAutoAtta<br/> chUpdateCommand.java:54)<span class="error">&#91;247:org.opendaylight.ovsdb.southbound-impl:1.2.2.SNAPSHOT&#93;</span></p> <p>Operating System: All<br/> Platform: All</p> OVSDB-317

Exception observed when ODL is added as OVS Manager

Bug Resolved Done Rashmi Pujar Venkatrangan Govindarajan Mon, 14 Mar 2016 00:09:32 +0000 Fri, 18 Mar 2016 22:16:53 +0000 Fri, 18 Mar 2016 22:16:53 +0000 unspecified Southbound.Open_vSwitch 0 7 <p>Attachment 5507_log.tgz has been added with description: Karaf log</p> <p><a href="https://jira.opendaylight.org/browse/MDSAL-135" title="Instantiated factory for class ... Ipv4Address outside its package" class="issue-link" data-issue-key="MDSAL-135"><del>MDSAL-135</del></a> also is related to this <a href="https://jira.opendaylight.org/browse/OVSDB-317" title="Exception observed when ODL is added as OVS Manager" class="issue-link" data-issue-key="OVSDB-317"><del>OVSDB-317</del></a>. There are exceptions from mdsal just before the exception described here in 5507.</p> <p>Messages logged in #5508 are warnings and do not affect functionality.</p> <p><a href="https://git.opendaylight.org/gerrit/36195" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/36195</a> should fix this.</p> <p>Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Beryllium without it? Is there a workaround such that we can write a release note and fix in Beryllium SR1?<br/> Testing: Could you also elaborate on the testing or this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests? <br/> Impact: Does this fix impact any dependent projects?</p> <p>Hi An,</p> <p> It affects VTN Openstack integration also. I will test both netvirt and VTN and update the bug with the status right now.</p> <p>(In reply to A H from comment #5)<br/> &gt; Severity: Could you elaborate on the severity of this bug? Is this a<br/> &gt; BLOCKER such that we cannot release Beryllium without it? Is there a<br/> &gt; workaround such that we can write a release note and fix in Beryllium SR1?<br/> &gt; Testing: Could you also elaborate on the testing or this patch? How<br/> &gt; extensively has this patch been tested? Is it covered by any unit tests or<br/> &gt; system tests? <br/> &gt; Impact: Does this fix impact any dependent projects?</p> <p>The bug is a blocker for any application using the ovsdb southbound with OVS versions &lt; 2.4. There is an exception in the connection code that fails the connection. Many projects use the ovsdb southbound - netvirt, gbp, vpnservice, vtn...</p> <p>Testing for the patch included connecting versions before and after OVS 2.4 and verifying the connection was successful.</p> <p>The jenkins IT test jobs check OVS versions 2.3.1 and 2.4 and the 2.3.1 job did have the problem. There were some other failures in the test runs so this failure was overlooked. Manual testing by Venkat highlighted the issue.</p> <p>The only workaround would be to use OVS versions 2.4 or later. I doubt that we could expect that solution.</p> <p>Tested the latest stable/Be code in ovsdb</p> <p> -&gt; Added ODL as Manager to OVS</p> <p> -&gt; Bridge created successfully as expected and the is_connected are true.</p> <p>Based on Venkatrangan Govindarajan comment #8, I assume this bug has been verified as fixed in the latest build for Beryllium SR1.</p> Development External issue ID 5507 External issue URL ODL SR Target Milestone Rank 0|i021zj: