[NETVIRT-213] flows is not correct when new vm created after the reconnection of ovs Created: 25/Oct/16  Updated: 06/Dec/16  Resolved: 06/Dec/16

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: wangqianyu Assignee: wangqianyu
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Zip Archive ovs-and-odl-data.zip    
External issue ID: 7016

 Description   

1. ovs connect to odl using below command
sudo ovs-vsctl set-manager tcp:10.43.174.155:6640
2. creat network, subnet, and vm on openstack.
the port and flows added to ovs please see the attachment
3. make the ovs reconnect to odl using follow commands
sudo ovs-vsctl set-manager tcp:127.0.0.1:6640
sudo ovs-vsctl set-manager tcp:10.43.174.155:6640
here, the datapath id will changed to a new one
4. creat new vm on the network, and then, the flows is not correct.
the reason is that: new port added to ovs causing new flow added
the added flow will be base on the new datapath id, the old flow on ovs would be overwrite



 Comments   
Comment by wangqianyu [ 25/Oct/16 ]

Attachment ovs-and-odl-data.zip has been added with description: ovs and odl data

Comment by Sam Hague [ 06/Dec/16 ]

https://git.opendaylight.org/gerrit/48187

Generated at Wed Feb 07 20:20:59 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.