[OVSDB-27] OVSDB-neutron does not set correct flows in case of OpenStack with VLAN networks Created: 25/Jun/14 Updated: 03/May/18 Resolved: 16/Sep/14 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | API |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vishal Patil | 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: | 1241 |
| Description |
|
Configuration 1) Devstack on Fedora 20 (https://wiki.opendaylight.org/images/HostedFiles/OpenDaylight_DevStack_Fedora20.ova) 2) Latest OVSDB (https://github.com/opendaylight/ovsdb) 3) OpenFlow 1.0 for OVS Problem Description: There seems to be a bug in ODL due to which the first VM booted on a compute node won't receive an IP. The reason being, ODL tries to program the flows on the internal bridges (br-int and br-net) before they are created and connected to the ODL. Thus the programming of flows fail. Any subsequent spawning of VMs on the compute nodes works fine, since the flow programming succeeds as the bridges have been already created (while spawning the first VM) |
| Comments |
| Comment by Vishal Patil [ 16/Sep/14 ] |
|
This bug isn't valid anymore. |