[OVSDB-337] Updates to OVSDB node fail on passively connected nodes Created: 13/May/16 Updated: 19/Oct/17 Resolved: 28/May/16 |
|
| 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 |
||
| External issue ID: | 5885 |
| Description |
|
When an OVSDB node is passively connected to the OVSDB plugin (i.e. the node initiates the connection to ODL), updates to the OVSDB node fail due to lack of connection-info information in the MD-SAL config. It is possible to configure bridge nodes and ports (termination-points) to a passively connected OVSDB node, so the issue is specifically with configuring the OVSDB node itself. A workaround is to supply connection-info to the OVSDB node config, but this requires looking up the remote tcp ephemeral port number for the connection. This is not desired - all of the required information is provided in the URL (e.g. the node-id for the OVSDB node). |
| Comments |
| Comment by Anil Vishnoi [ 24/May/16 ] |
|
master : https://git.opendaylight.org/gerrit/38886 |