[NETVIRT-240] Pipeline flows are not consistently installed on OVS node with pre-existing integration bridge Created: 05/Nov/16 Updated: 09/Mar/18 Resolved: 16/Nov/16 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | None |
| Affects Version/s: | Boron |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Bertrand Low | Assignee: | Bertrand Low |
| 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: | 7093 |
| Description |
|
On an OVS switch that has an existing integration bridge (e.g. br-int) before set-manager is called, the pipeline flows for that bridge may not always get installed on the switch once set-manager is called. e.g. [root@odl32 odl]# ovs-vsctl show |
| Comments |
| Comment by Bertrand Low [ 05/Nov/16 ] |
|
On debugging, it appears that netvirt is causing a dpid change on the OVS switch by sending down a new hw_addr (MAC) when ODL connects. The changing dpid in turn causes the connection to flap between ODL and the bridge as OVS reconnects to advertise the new dpid. This connection flap does not allow for reliable installation of the pipeline flows on the switch. The details of this bug are captured on the email thread: |
| Comment by Bertrand Low [ 05/Nov/16 ] |
|
Submitted this patch to stable/boron: |
| Comment by Bertrand Low [ 16/Nov/16 ] |
|
Cherry-picked into master: |