And this second test report is when I just apply ofplugin Li patch [2]: https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/296/robot/report/log.html <https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/296/robot/report/log.html>
I see SAME issues as with l2switch Li plugin patch + some weird topology display issue (internal topology works as otherwise ping would not work but switch links are not shown) the second time we run Host Tracker test. BR/Luis [2] https://git.opendaylight.org/gerrit/#/c/35892/ <https://git.opendaylight.org/gerrit/#/c/35892/> > On Apr 13, 2016, at 7:32 PM, Luis Gomez <[email protected]> wrote: > > From today’s l2switch call, I got action point to run system test on Li patch > [1]: > > https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/291/robot/report/log.html > > <https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-switch-only-boron/291/robot/report/log.html> > > From the result above we can observe following issues: > > - Flow push: There is no LLDP flows being pushed. Also flood flows seem to be > in config space because operational shows flow ID. > - Address Tracker: All host IP addresses are seeing in all nodes, that is not > right, only node connected to host should show the host. > - Host Tracker: After remove/add OpenFlow port (ovs-vsctl add-port), no host > is learned anymore through that port. > - Loop Remover: Not working, using a loop topology, even when we observe some > ports are in DISCARD mode, mininet sees DUP packets. > > BR/Luis > > [1] https://git.opendaylight.org/gerrit/#/c/33303/ > <https://git.opendaylight.org/gerrit/#/c/33303/> > >
_______________________________________________ L2switch-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/l2switch-dev
