[L2SWITCH-45] Hostracker module does not remove host after host link goes down Created: 23/May/15  Updated: 19/Oct/17

Status: Confirmed
Project: l2switch
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

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

Operating System: All
Platform: All

Issue Links:
Duplicate
is duplicated by L2SWITCH-15 L2switch : l2switch doesn't remove ru... Resolved
External issue ID: 3346
Priority: Low

 Description   

I guess related with 1995.

To reproduce:

  • start controller with odl-l2switch-switch-ui feature
  • start mininet any topology with hosts
  • do pingall
  • check discovered hosts in topology UI or REST API
  • disconnect host link: link h1 s1 down
  • host is still in topology

BR/Luis

 Comments   
Comment by Luis Gomez [ 08/Sep/15 ]

I changed the title so this bug does not get confused with removing ports from switches.

Comment by Sai MarapaReddy [ 19/Apr/16 ]

Host will expire if there is no traffic associated with it after a while BUG5012 (https://bugs.opendaylight.org/show_bug.cgi?id=5012). We have fix for it, waiting for review (https://git.opendaylight.org/gerrit/#/c/33928/ ).

When a link is down, there is no change in topology, but in reactive flood mode using the above mentioned patch we remove all the expired hosts ( since link is down - associated hosts will be expected to expire )

Will the above patch address the issue or do we need immediate changes in topology ?

Comment by Sai MarapaReddy [ 27/Apr/16 ]

Luis says if the time out is too long, user may not wait long time.

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