Re: [L2switch-dev] [openflowplugin-dev] Blocker bug analysis

2016-10-19 Thread Luis Gomez
Hi Sai, after looking at the test more in detail this is not exactly the behavior (sorry for the confusion), what is really happening is: - Mininet restarts - There is no host in address-tracker after restart - We do the classic mininet pingall test - After the pingall test the host addresses

Re: [L2switch-dev] [openflowplugin-dev] Blocker bug analysis

2016-10-18 Thread Luis Gomez
Actually this is the drop flow so it is expected, anyway going deeper into l2switch test issues I see: - The address tracker issue is because hosts addresses are not getting cleared when we restart mininet with no sleep in-between. - The loop remover issue could be related to some test issue, I

Re: [L2switch-dev] [openflowplugin-dev] Blocker bug analysis

2016-10-17 Thread Shuva Jyoti Kar
Latest on this. The bug description changed a bit over the weekend. the issue was seen with big flows (lot of matches) just adding (no deleting) different big flows every 8 secs. I tried it around 13 times today back-to-back with 8 secs gap in between , but was not able to hit the issue. I

Re: [L2switch-dev] [openflowplugin-dev] Blocker bug analysis

2016-10-17 Thread Miroslav Macko
Hello Luis and dev guys, There is this info from l2-switch in the karaf log: 2016-10-14 22:43:24,941 | INFO | pool-16-thread-1 | FlowWriterServiceImpl | 229 - org.opendaylight.l2switch.main.impl - 0.5.0.SNAPSHOT | In addMacToMacFlowsUsingShortestPath: No flows added. Source and

Re: [L2switch-dev] [openflowplugin-dev] Blocker bug analysis

2016-10-15 Thread Shuva Jyoti Kar
About 6917, I have updated the bug with my observations. Tried it about 23 times(add/get/del) in successions of 5 secs(used a stopwatch) but could see the alien flow id in oper DS only once, and that too the moment I tried a re-get it vanished. I did use a different flow object, but I donot

Re: [L2switch-dev] [openflowplugin-dev] Blocker bug analysis

2016-10-14 Thread Tomáš Slušný
Also, 6710 was already merged only in master branch, but not yet in boron. It have cherry-pick ready here: https://git.opendaylight.org/gerrit/#/c/46761/, but until it is merged, I think it would be better to check for improvement in Jenkins test for Carbon here:

Re: [L2switch-dev] [openflowplugin-dev] Blocker bug analysis

2016-10-14 Thread Tomáš Slušný
​6710 was related to both cluster and single node, because even in single node scenario, we are registering to ClusterSingletonService, what had problems when we tried to re-register, when we do not fully closed previous registration (so, when we disconnected and reconnected too fast). Most

Re: [L2switch-dev] [openflowplugin-dev] Blocker bug analysis

2016-10-14 Thread Luis Gomez
No luck :), still fails on "address tracker" and "loop remover": https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-carbon/154/ https://logs.opendaylight.org/releng/jenkins092/l2switch-csit-1node-switch-only-carbon/154/archives/log.html.gz BR/Luis > On

Re: [L2switch-dev] [openflowplugin-dev] Blocker bug analysis

2016-10-14 Thread Luis Gomez
OK Tomas, I will try your patch https://git.opendaylight.org/gerrit/#/c/46390/ on l2switch-csit-1node-switch-only-carbon and let you know. > On Oct 14, 2016, at 1:23 PM, Tomáš Slušný wrote: > > Also, 6710 was already merged only in master branch, but not yet in