[NETVIRT-260] Attaching new interface to VM does not install flow in the OVS for the new interface Created: 09/Nov/16  Updated: 19/Oct/17  Resolved: 08/Dec/16

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

Type: Bug
Reporter: Michael Dulberg Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File q-svc.rar     File screen-karaf.rar    
Issue Links:
Duplicate
duplicates OPNFLWPLUG-790 failed to update port status - all ne... Resolved
External issue ID: 7132
Priority: Normal

 Description   

a. Create net1, net2
b. Net1- 111.111.111.0/24 , net2- 222.222.222.0/24
c. Both have their own default gw- 111.111.111.254 , 222.222.222.254
d. Add router interfaces
e. Add VM1 to net1 (111.111.111.2) and VM2 to net2 (222.222.222.2)
f. Ping works fine
g. Change default gw on net1 to 111.111.111.250
a. Need to delete the router interface, then change the gw in the network and then change it in the VM as well
h. Ping works fine
i. < here I played a bit with FIP- adding removing etc. worked fine>
j. Attach net1 interface to VM2 (111.111.111.3)
k. Add interface info in the VM-
i. sudo ip addr add 111.111.111.3/24 dev eth1
ii. sudo ip link set eth1 down
iii. sudo ip link set eth1 up
iv. verify route –n was added properly
l. Ping from VM2 to VM1  doesn’t work.
m. I see no rule for the new interface in table 50 or 51

 Comments   
Comment by Michael Dulberg [ 09/Nov/16 ]

Attachment q-svc.rar has been added with description: q-svc logs

Comment by Michael Dulberg [ 09/Nov/16 ]

Attachment screen-karaf.rar has been added with description: karaf logs

Comment by Yair Zinger [ 08/Dec/16 ]

I was unable to reproduce it.
The logs information is not enough to understand the cause.

We need to reproduce it and get the datastore state and trace level logs.

Comment by Koby Aizer [ 08/Dec/16 ]

Yair & I another look and the root cause is OPNFLWPLUG-790 in openflowplugin (https://bugs.opendaylight.org/show_bug.cgi?id=6908)

You can see this message in the log:
2016-11-09 15:36:49,471 | WARN | entLoopGroup-9-1 | DeviceContextImpl | 291 - org.opendaylight.openflowplugin.impl - 0.3.1.SNAPSHOT | Error processing port status message for port 294 on device Uri [_value=openflow:215763471863001] : java.lang.IllegalStateException: Previous transaction member-1-datastore-operational-fe-0-chn-8-txn-706 is not ready yet

This means the ODL fails to receive port up updates from the OVS, and therefore the interface configuration is not complete.

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