[OVSDB-192] pipeline flows not programmed because controller address is not set on OVSDB node Created: 13/Aug/15 Updated: 19/Oct/17 Resolved: 08/Sep/15 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | openstack.net-virt-providers |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Sam Hague | 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: | 4135 |
| Description |
|
In some cases the controller config is not pushed to the OVSDB node and switch so flows are not installed on the switch. In this scenario the pipeline flows are written to config but they don't get pushed to the switch. |
| Comments |
| Comment by Flavio Fernandes [ 16/Aug/15 ] |
|
In my setup, I hit this issue. It looks like the config is pushed to another br-ex bridge, which is In the example below, you can see that bridge 'delta' is the one – [vagrant@devstack-control devstack]$ /opt/tools/showOvsdbMdsal.py --config Bridges in ovsdb://uuid/17d1993c-7205-417d-bc4f-f314ecb9f0b1 config tree flows at alpha config tree flows at bravo config tree flows at charlie config tree flows at openflow:147594668038470 ( node_not_in_topology ) [vagrant@devstack-control devstack]$ ===== OPERATIONAL: [vagrant@devstack-control devstack]$ /opt/tools/showOvsdbMdsal.py ovsdbNode:192.168.50.20:40870 mgr:192.168.50.20:6640 version:2.3.1 operational tree flows at alpha operational tree flows at bravo operational tree flows at charlie operational tree flows at delta ofLinks (discover via lldp): [vagrant@devstack-control devstack]$ |
| Comment by Sharad Mishra [ 08/Sep/15 ] |
|
patch merged - https://git.opendaylight.org/gerrit/#/c/26166/ |