(Resending with less content and changing title) Here is the run with your patch:
https://jenkins.opendaylight.org/releng/job/l2switch-csit-1node-switch-only-boron/795/ <https://jenkins.opendaylight.org/releng/job/l2switch-csit-1node-switch-only-boron/795/> Please let us know if we can help with anything. BR/Luis > On Oct 20, 2016, at 10:54 AM, Sai MarapaReddy <[email protected] > <mailto:[email protected]>> wrote: > > Done. Thanks Jamo. > > On Thu, Oct 20, 2016 at 10:39 AM, Jamo Luhrsen <[email protected] > <mailto:[email protected]>> wrote: >> >> >> On 10/19/2016 11:26 PM, Sai MarapaReddy wrote: >> > Address tracker tries [1] to read any existing address from data store. My >> > guess is in the case of immediate restart of >> > mininet , addresses from data store are not cleaned and this is why we see >> > all addresses. >> > >> > In further attempt to verify this information I have a patch here [2]. I >> > tried running it with keyword "test-l2switch-all" >> > but no success. Could you please run it. This might help in >> > troubleshooting the issue further. >> >> it's because we don't have a patch test job for l2switch yet. It's >> something projects are adding >> on an as-needed basis. I gave you one here: >> >> https://git.opendaylight.org/gerrit/#/c/47219/ >> <https://git.opendaylight.org/gerrit/#/c/47219/> >> >> give it a +1 and we can try to get it merged. >> >> Thanks, >> JamO >> >> >> > [1] >> > https://github.com/opendaylight/l2switch/blob/stable/boron/addresstracker/implementation/src/main/java/org/opendaylight/l2switch/addresstracker/addressobserver/AddressObservationWriter.java#L116 >> > >> > <https://github.com/opendaylight/l2switch/blob/stable/boron/addresstracker/implementation/src/main/java/org/opendaylight/l2switch/addresstracker/addressobserver/AddressObservationWriter.java#L116> >> > >> > [2] https://git.opendaylight.org/gerrit/#/c/47186/ >> > <https://git.opendaylight.org/gerrit/#/c/47186/> >> > >> > On Wed, Oct 19, 2016 at 9:43 AM, Luis Gomez <[email protected] >> > <mailto:[email protected]> <mailto:[email protected] >> > <mailto:[email protected]>>> wrote: >> > >> > 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 (10.0.0.1, 10.0.0.2, >> > 10.0.0.3) are seen in all switches, while in normal >> > scenario 10.0.0.1 should be only in s1 to-host port, 10.0.0.2 should >> > be only in s2 to-host port and 10.0.0.3 should be >> > only in s3 to-host port. >> > >> > The normal scenario happens when we leave 2 secs between mininet stop >> > + start. >> > >> > So 2 questions: >> > >> > - What is the impact of address tracker registering remote IP >> > addresses in the switch-to-switch ports? As far as I can >> > see flows are generated correctly even in this case. >> > - Any idea why the address tracker would get confused and add IP >> > addresses to the switch-to-switch ports? maybe the >> > application fails to identify these ports as going switch-to-switch? >> > >> > BR/Luis >> >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
