[OPNFLWPLUG-759] l2switch addresss tracker does not behave normally when mininet is disconnected and connected with no time in-between Created: 29/Aug/16  Updated: 27/Sep/21  Resolved: 06/Mar/17

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

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

Operating System: All
Platform: All


Issue Links:
Blocks
is blocked by MDSAL-197 Switch connection bounce results in w... Resolved
External issue ID: 6575
Priority: Highest

 Description   

l2switch csit is not stable in boron:

https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/

however tests pass if we add some time between disconnect and connect mininet between tests:

https://git.opendaylight.org/gerrit/#/c/44799/

This explains why testing manually does not show any issue.



 Comments   
Comment by Sai MarapaReddy [ 13/Sep/16 ]

Openflowplugin project might be right place for the bug.

Comment by Sai MarapaReddy [ 04/Oct/16 ]

l2switch csit jobs fail because of this bug. Can you please address the issue.

Comment by Shuva Jyoti Kar [ 07/Oct/16 ]

Since manually we are not seeing any issues , do we add a delay between the switch disconnect and connect ?

Comment by Tomas Slusny [ 07/Oct/16 ]

No no no, this is a problem. I think it is related to MDSAL-197 and 6672, and when that bugs will be fixed, this one will probably be fixed too.

Comment by Shuva Jyoti Kar [ 07/Oct/16 ]

(In reply to Tomas Slusny from comment #4)
> No no no, this is a problem. I think it is related to MDSAL-197 and 6672, and
> when that bugs will be fixed, this one will probably be fixed too.

ok sure

Comment by Tomas Slusny [ 07/Oct/16 ]

Read my last reply in OPNFLWPLUG-767

Comment by A H [ 13/Oct/16 ]

Based on the comments, I believe this bug is targeted for Boron.

Comment by A H [ 25/Oct/16 ]

Based on the comment on the email thread below, this bug is being retargeted for Boron-SR2:

https://lists.opendaylight.org/pipermail/l2switch-dev/2016-October/001322.html

Comment by Shuva Jyoti Kar [ 10/Dec/16 ]

Based on the comment in the mail thread below this bug is targeted for Boron-SR3:
https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-December/006456.html

Comment by Luis Gomez [ 13/Dec/16 ]

I will set importance to CRITICAL because as far as I can tell there is no traffic impact but a change in the address-tracker behavior: host addresses are observed in ports besides the port the host is connected to.

Comment by Luis Gomez [ 13/Dec/16 ]

See mail thread:

https://lists.opendaylight.org/pipermail/l2switch-dev/2016-October/001322.html

Comment by Abhijit Kumbhare [ 23/Feb/17 ]

Luis & Sai,

Is this fixed? Tomas seems to have said that once MDSAL-197 and OPNFLWPLUG-767 are fixed - then this will be fixed. Now both those bugs are fixed - so good to recheck it.

Abhijit

Comment by Luis Gomez [ 06/Mar/17 ]

So l2switch issue seems to be fixed but very recently so I believe it was something else other than the 2 patches you mention:

https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/

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