[YANGTOOLS-554] java.lang.IllegalArgumentException: Unsupported modification APPEARED (Again) Created: 20/Nov/15 Updated: 10/Apr/22 Resolved: 09/Jan/16 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Anil Vishnoi | Assignee: | Tony Tkacik |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| External issue ID: | 4657 | ||||||||
| Priority: | High | ||||||||
| Description |
|
I see following exception when i start my 3 node ovsdb cluster 2015-11-20 20:49:15,894 | WARN | ult-dispatcher-4 | ShardManager | 150 - org.opendaylight.controller.sal-distributed-datastore - 1.3.0.SNAPSHOT | Supervisor Strategy caught unexpected exception - resuming |
| Comments |
| Comment by Robert Varga [ 24/Nov/15 ] |
|
Are there steps to reproduce? Can you describe what operations ovsdb has executed on the data store and what their results were? Full karaf logs from all nodes are also required, as it seems that the cluster underwent a leadership change while active operations were being executed. |
| Comment by Anil Vishnoi [ 05/Jan/16 ] |
|
Karaf log from controller-1 in 3-node cluster setup of ovsdb. |
| Comment by Anil Vishnoi [ 05/Jan/16 ] |
|
Attachment karaf-c1.log has been added with description: Karaf-Log-Controller-1 |
| Comment by Anil Vishnoi [ 05/Jan/16 ] |
|
Karaf log from controller-1 in 3-node cluster setup of ovsdb. |
| Comment by Anil Vishnoi [ 05/Jan/16 ] |
|
Attachment karaf-c2.log has been added with description: Karaf-Log-Controller-2 |
| Comment by Anil Vishnoi [ 05/Jan/16 ] |
|
Karaf log from controller-3 in 3-node cluster setup of ovsdb. |
| Comment by Anil Vishnoi [ 05/Jan/16 ] |
|
Attachment karaf-c3.log has been added with description: Karaf-Log-Controller-3 |
| Comment by Anil Vishnoi [ 05/Jan/16 ] |
|
Following are the steps to re-create the issue 1) configure 3-node cluster using the ovsdb project ( standard setting) wait for cluster to come up and you will see this exception. The only operation ovsdb does before this exception is writing "netvirt:1" node on /topology/ but that's around 700ms before. 2016-01-05 01:12:58,056 | INFO | lt-dispatcher-15 | SouthboundProvider | 233 - org.opendaylight.ovsdb.southbound-impl - 1.2.1.SNAPSHOT | Initialize OVSDB topology Uri [_value=ovsdb:1] in operational and config data store if not already present |
| Comment by Anil Vishnoi [ 05/Jan/16 ] |
|
please let me know if you need more details. Thanks |
| Comment by Tony Tkacik [ 08/Jan/16 ] |