[NETVIRT-1395] Netvirt 3 node CSIT - ELAN fails to program Table 51 actions in random cases Created: 07/Aug/18  Updated: 06/Nov/18  Resolved: 06/Nov/18

Status: Resolved
Project: netvirt
Component/s: elanmanager
Affects Version/s: None
Fix Version/s: Fluorine-SR1

Type: Bug Priority: Medium
Reporter: Faseela K Assignee: Aswin Suryanarayanan
Resolution: Cannot Reproduce Votes: 0
Labels: csit:3node, csit:failures
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

While running l2 suite in netvirt 3 node CSIT randomly, ELAN intermittently fails to program the right actions in Table 51 for the destination mac, rather a drop action is programmed for the MAC.

This can be a race condition in ELAN, in the way it fetches getEgressActionsForInterface() from genius.

 Comments   
Comment by Faseela K [ 07/Aug/18 ]

https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/builder-copy-sandbox-logs/322/faseela-l2-netvirt-csit-3node-0cmb-1ctl-2cmp-openstack-queens-upstream-stateful-oxygen/6/

Thanks a lot xcheara for debugging the failure!

Comment by Chetan Arakere Gowdru [ 07/Aug/18 ]

Observed in table=51 on the destination VM(21.0.0.4) DPN, remote actions where set to drop action.

cookie=0x8031771, duration=233.978s, table=51, n_packets=3, n_bytes=126, priority=20,metadata=0x1771000000/0xffff000000,dl_dst=fa:16:3e:02:0c:f7 actions=drop

fa:16:3e:02:0c:f7 - 21.0.0.12

 

So, the reverse/response traffic is getting dropped.

Comment by Jamo Luhrsen [ 16/Aug/18 ]

k.faseela, xcheara any update here?

Comment by Faseela K [ 17/Aug/18 ]

jluhrsen : aswins has taken up the bug, and he told he will take a look at this. Time to bug him

Comment by Aswin Suryanarayanan [ 20/Aug/18 ]

I am working on a similar bug.Planning to work on this after that.

Comment by Jamo Luhrsen [ 12/Sep/18 ]

any update on this one aswins

Comment by Aswin Suryanarayanan [ 16/Oct/18 ]

stuck with other works , didn't spend much cycle in this one till now.

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