[OVSDB-298] No candidates are selected after fail and restart owner and candidate 2 times Created: 11/Feb/16  Updated: 19/Oct/17  Resolved: 17/May/16

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

Type: Bug
Reporter: Priya Ramasubbu Assignee: Anil Vishnoi
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Zip Archive ControllerLogs.zip    
External issue ID: 5321

 Description   

I test ovsdb 3 node cluster

Following are the steps which i tried in csit
1. Create a 3 nodes cluster sessions
2. I made the owner instance down and with two nodes i verified the data sharding, it works well
3. I restarted the killed owner, now with the 3 nodes tests works fine.
4. I made the non owner instance down and with the existing two nodes tests works fine.
5. I restarted the killed non owner, now with the 3 nodes tests works fine.
6. I deleted the ovsdb node and deleted all the sessions.

First time execution of test cases works well.

I re run the above steps, where i could not find the entity owners when all the three nodes are up.

In the log there is an unexpected response for entity owner get request /restconf/operational/entity-owners:entity-owners.
The response is ,

[ '{"entity-owners":{"entity-type":[{"type":"ovsdb","entity":[

{"id":"/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\'ovsdb:1\']/network-topology:node[network-topology:node-id=\'ovsdb://uuid/a96ec4e2-c457-4a2c-963c-1e6300210032\']","owner":""}

,{"id":"/network-topology:network-topology/network-topology:topology[network-topology:topology-id=\'ovsdb:1\']/network-topology:node[network-topology:node-id=\'ovsdb://uuid/d8a057af-9317-46dc-a017-99c7e1c6ef1c\']","owner":"member-3",
"candidate":[

{"name":"member-3"}

]}]},
{"type":"ovsdb-southbound-provider","entity":[{"id":"/general-entity:entity[general-entity:name=\'ovsdb-southbound-provider\']","owner":"member-2","candidate":[

{"name":"member-2"}

,

{"name":"member-1"}

,

{"name":"member-3"}

]}]}]}}' ]

In the Candidate attribute for entity type "ovsdb" the two nodes which i made down and up are not there in the candidate list.

Here goes the sandbox links for full trace of karaf logs:
https://jenkins.opendaylight.org/sandbox/job/ovsdb-csit-3node-clustering-only-beryllium/27/

Please let us know if any more details needed.



 Comments   
Comment by Priya Ramasubbu [ 11/Feb/16 ]

Attachment ControllerLogs.zip has been added with description: 3 odl Controller Logs

Comment by Luis Gomez [ 15/Feb/16 ]

This is a bug in the robot test. Current "get entity owner" keyword cannot deal with more than one ovs uuid, which means it will fail after restarting the ovs connection in step 6 + step 1.

Fix for this is here: https://git.opendaylight.org/gerrit/#/c/34652/

BR/Luis

Comment by Luis Gomez [ 26/Feb/16 ]

Reopening the bug and changing the title to better describe the issue. We need to provide easy steps for manual reproduction.

Comment by Anil Vishnoi [ 08/Mar/16 ]

Luis, any update on this bug?

Comment by Anil Vishnoi [ 17/May/16 ]

Hi Luis/Priya,

It's been a while there is no update on this bug. I am closing this bug, if you still see the issue and able to recreate it locally, please reopen the bug.

Thanks
Anil

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