Details
-
Bug
-
Status: Resolved
-
Medium
-
Resolution: Done
-
Boron
-
None
-
None
-
None
-
Operating System: All
Platform: All
-
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:
- create network/subnet
- create SG sg1
- create egress TCP rule from command line below:
neutron security-group-rule-create --direction egress --protocol tcp --ethertype IPv4
- create vm1 with sg1
- expect: flow entries for allowing tcp egress from the vm added to the switch
- actual: no flow entries for allowing tcp egress added to the switch
This issue might happen for adding TCP ingress rule and UDP ingress/egress rules to VM as well.