[SFC-221] SFC get the null egress vxlan-gpe ports Created: 22/Jun/18 Updated: 23/Aug/18 |
|
| Status: | Open |
| Project: | sfc |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Qiuzheng Ren | Assignee: | Brady Johnson |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Sometimes the ovs has two same vxlan-gpe ports ,one port is effective and another port number is null. For example : [root@wlz-controller ~]# ovs-vsctl show When sfc gert the egress vxlan-gpe port, it maybe get the null port. As a result , the flow table is wrong. |
| Comments |
| Comment by Jaime Caamaño Ruiz [ 05/Jul/18 ] |
|
Which port is the null port on that output? Port "tun162d5c0de6a" Port "tun6f0e9979c0b" I am surprised about that, I would think OVS would not allow to create two tunnel ports with the same parameters twice. |
| Comment by Qiuzheng Ren [ 23/Aug/18 ] |
|
But the ovs really create two tunnel ports and one of the ports does not have the port number. [root@wlz-controller odl]# ovs-vsctl show [root@wlz-controller odl]# ovs-ofctl show -O Openflow13 br-int
We can see through the command "ovs-vsctl show ",there is two tunnel ports. and only one tunnel has the port number. I don't know why it happens. The netvirt module can select the correct tunnel ports and write correct flow tables. I suspect it maybe caused by netvirt. |