[NETVIRT-499] Flows not added for TCP security group rule with no min/max Created: 28/Feb/17 Updated: 09/Mar/18 Resolved: 09/Mar/18 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | None |
| Affects Version/s: | Boron |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Vinh Nguyen | 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: | 7863 |
| Description |
|
ODL version: Boron SR2 When add a simple TCP egress rule from command line, there is no flow added to the OVS even though karaf log shows the flow is written successfully. Steps to reproduce:
neutron security-group-rule-create --direction egress --protocol tcp --ethertype IPv4
This issue might happen for adding TCP ingress rule and UDP ingress/egress rules to VM as well. |
| Comments |
| Comment by Vinh Nguyen [ 28/Feb/17 ] |
|
The ovs-vswitch shows the following errors flow entries for the TCP/UDP all range are pushed down: 2017-02-28T11:21:30.508Z|00126|meta_flow|WARN|source field tcp_dst lacks correct prerequisites Further investigation shows that the flow entry does not have the layer 4 information, hence the error messages |
| Comment by Vinh Nguyen [ 01/Mar/17 ] |
|
Code review: |