[OVSDB-317] Exception observed when ODL is added as OVS Manager Created: 14/Mar/16  Updated: 18/Mar/16  Resolved: 18/Mar/16

Status: Resolved
Project: ovsdb
Component/s: Southbound.Open_vSwitch
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Venkatrangan Govindarajan Assignee: Rashmi Pujar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File 5507_log.tgz    
External issue ID: 5507

 Description   

The following are the setup details.

ovsdb:latest stable/beryllium source (5 PM PST on 13-March-2016)

OVS: version: 2.3.2

Steps:

1. Start Karaf

2. Install feature: odl-ovsdb-openstack

3. Add ODL as OVS Manager usinf sudo ovs-vsctl set-manager tcp:ODL_IP:6640

4. Expectation: br-int gets creaeted, br-ex may get creaetd (if l3_fwd is enabled at ODL) and is_connected becomes true

Actual: Only is_connected becomes true

Observation: Exceptions in karaf.log

16-03-13 23:55:57,480 | ERROR | ult-dispatcher-5 | EntityOwnershipListenerActor | 165 - org.opendaylight
.controller.sal-distributed-datastore - 1.3.1.SNAPSHOT | Error notifying listener org.opendaylight.ovsdb.south
bound.OvsdbConnectionManager$OvsdbDeviceEntityOwnershipListener@735f4b78
java.lang.IllegalArgumentException: Not able to create instance of class class org.opendaylight.ovsdb.lib.sche
ma.GenericTableSchema using public constructor that accepts TableSchema object
at org.opendaylight.ovsdb.lib.schema.DatabaseSchema.createTableSchema(DatabaseSchema.java:80)[244:org.
opendaylight.ovsdb.library:1.2.2.SNAPSHOT]
at org.opendaylight.ovsdb.lib.schema.DatabaseSchema.table(DatabaseSchema.java:62)[244:org.opendaylight
.ovsdb.library:1.2.2.SNAPSHOT]
at org.opendaylight.ovsdb.lib.schema.typed.TyperUtils.getTableSchema(TyperUtils.java:55)[244:org.opend
aylight.ovsdb.library:1.2.2.SNAPSHOT]
at org.opendaylight.ovsdb.lib.schema.typed.TyperUtils.extractRowUpdates(TyperUtils.java:515)[244:org.o
pendaylight.ovsdb.library:1.2.2.SNAPSHOT]
at org.opendaylight.ovsdb.lib.schema.typed.TyperUtils.extractRowsUpdated(TyperUtils.java:425)[244:org.
opendaylight.ovsdb.library:1.2.2.SNAPSHOT]
at org.opendaylight.ovsdb.southbound.transactions.md.OvsdbAutoAttachUpdateCommand.<init>(OvsdbAutoAtta
chUpdateCommand.java:54)[247:org.opendaylight.ovsdb.southbound-impl:1.2.2.SNAPSHOT]

 Comments   
Comment by Venkatrangan Govindarajan [ 14/Mar/16 ]

Attachment 5507_log.tgz has been added with description: Karaf log

Comment by Sam Hague [ 14/Mar/16 ]

MDSAL-135 also is related to this OVSDB-317. There are exceptions from mdsal just before the exception described here in 5507.

Comment by Robert Varga [ 14/Mar/16 ]

Messages logged in #5508 are warnings and do not affect functionality.

Comment by Stephen Kitt [ 14/Mar/16 ]

https://git.opendaylight.org/gerrit/36195 should fix this.

Comment by A H [ 14/Mar/16 ]

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?
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?
Impact: Does this fix impact any dependent projects?

Comment by Venkatrangan Govindarajan [ 14/Mar/16 ]

Hi An,

It affects VTN Openstack integration also. I will test both netvirt and VTN and update the bug with the status right now.

Comment by Sam Hague [ 14/Mar/16 ]

(In reply to A H from comment #5)
> 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?
> 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?
> Impact: Does this fix impact any dependent projects?

The bug is a blocker for any application using the ovsdb southbound with OVS versions < 2.4. There is an exception in the connection code that fails the connection. Many projects use the ovsdb southbound - netvirt, gbp, vpnservice, vtn...

Testing for the patch included connecting versions before and after OVS 2.4 and verifying the connection was successful.

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.

The only workaround would be to use OVS versions 2.4 or later. I doubt that we could expect that solution.

Comment by Venkatrangan Govindarajan [ 14/Mar/16 ]

Tested the latest stable/Be code in ovsdb

-> Added ODL as Manager to OVS

-> Bridge created successfully as expected and the is_connected are true.

Comment by A H [ 18/Mar/16 ]

Based on Venkatrangan Govindarajan comment #8, I assume this bug has been verified as fixed in the latest build for Beryllium SR1.

Generated at Wed Feb 07 20:36:05 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.