[OVSDB-178] Config datastore empty on reconnect to ovsdb-node Created: 18/Jun/15 Updated: 19/Oct/17 Resolved: 29/Sep/15 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Southbound.Open_vSwitch |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Chaudhry Muhammad Usama | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| External issue ID: | 3796 |
| Description |
|
If the connection to the OVS node is deleted but the br-int remains in it and controller is not restarted. Now, if the controller is again connected to the OVS node. The controller doesn't create the br-int bridge so the br-int remains in the operational topology but not in the config data-store. |
| Comments |
| Comment by Sam Hague [ 29/Sep/15 ] |
|
Chaudhry, I didn't follow what you were saying.
While using "odl-ovsdb-openstack" feature. The br-int is automatically created as soon as you connect your controller to the OVS. There was an issue that if the connection to the OVS is deleted while the br-int entry is in the topology. On Reconnect, the br-int entry is not added into the config data store but the bridge remains in the operational topology. So that was the issue which has been resolved.
|