[OVSDB-186] Posting multiple OVSDB nodes with different node-id but same connection-info does not clean operational MD-SAL Created: 13/Jul/15  Updated: 19/Oct/17  Resolved: 11/Oct/15

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

Type: Bug
Reporter: Eric Multanen Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 3989

 Description   

If an active OVSDB connection is made via the config MD-SAL to the same
OVS host (IP address, port number) multiple times with different node-ids
then:

1. multiple entries are made in the config MD-SAL - 1 for each node-id
2. multiple sets of entries are made in the operational MD-SAL - 1 set for each node-id

If the config MD-SAL entries are then deleted, then:

1. All of the config MD-SAL entries are removed
2. Only the most recent operational MD-SAL set is removed. The older operational MD-SAL sets of entries corresponding to the config entry node-ids entered prior to the last one remain in the operational MD-SAL.

Better behavior could be:
1. don't allow a new config MD-SAL entry to be made to the same connection-info if there is already a config MD-SAL entry for the connection.

2. Or, allow the new config MD-SAL entry, but make sure to delete the old operational MD-SAL information.

3. Or, ... ?



 Comments   
Comment by Sam Hague [ 11/Oct/15 ]

https://git.opendaylight.org/gerrit/#/c/26118/

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