Pushing master or slave role to device is failing . If you are using single node controller, as a workaround you can enable the "equal-role=enabled" config knob in openflowplugin.cfg file.
On Mon, Oct 29, 2018 at 4:16 AM Jaime Caamaño Ruiz <jcaam...@suse.de> wrote: > Ok, a third restart did eventually help ;) > > -----Original Message----- > From: Jaime Caamaño Ruiz <jcaam...@suse.de> > Reply-to: jcaam...@suse.com > To: Jamo Luhrsen <jluhr...@gmail.com>, openflowplugin-dev@lists.openday > light.org > Subject: Re: [openflowplugin-dev] openflow connections problems > Date: Mon, 29 Oct 2018 11:08:59 +0100 > > Hey Jamo > > The error is the same but it does not tell much in itself and I am not > operating a cluster. Restarting the single ODL does not help in my > case. > > BR > Jaime. > > -----Original Message----- > From: Jamo Luhrsen <jluhr...@gmail.com> > To: openflowplugin-dev@lists.opendaylight.org, jcaam...@suse.de > Subject: Re: [openflowplugin-dev] openflow connections problems > Date: Thu, 25 Oct 2018 09:07:21 -0700 > > Jaime, > > any chance you are hitting this? > > https://jira.opendaylight.org/browse/OPNFLWPLUG-1035 > > JamO > > On 10/25/18 5:18 AM, Jaime Caamaño Ruiz wrote: > > Hello > > > > Randomly I sometimes get an OVS (2.9.2) switch to which ODL cannot > > connect because MASTER role cannot be set. At the end, the only > > traces > > indicative of the problem. No other ERROR/WARNS are printed. Attached > > a > > capture. It looks like the multipart reply OFPMP_DESC is never > > processed properly, but nowhere shows why. > > > > Any hints? > > > > Thanks > > Jaime > > > > 2018-10-25T05:14:33,047 | WARN | epollEventLoopGroup-9-2 | > > ContextChainImpl | 379 - > > org.opendaylight.openflowplugin.impl - 0.8.0.SNAPSHOT | Not able to > > start clustering services for node openflow:185574002334271 > > 2018-10-25T05:14:33,047 | WARN | ofppool-11 | > > ContextChainHolderImpl | 379 - > > org.opendaylight.openflowplugin.impl - 0.8.0.SNAPSHOT | Not able to > > set > > MASTER role on device openflow:185574002334271, reason: > > java.lang.RuntimeException: Failed to initialize device > > openflow:185574002334271 in 9s: > > java.util.concurrent.TimeoutException: > > Waited 9000 milliseconds for > > com.google.common.util.concurrent.Abstract > > TransformFuture$AsyncTransformFuture@52c8e28d[status=PENDING, > > info=[inputFuture=[com.google.common.util.concurrent.AbstractTransfor > > mF > > uture$TransformFuture@30c900ec[status=PENDING, > > info=[inputFuture=[com.g > > oogle.common.util.concurrent.SettableFuture@7015a912[status=PENDING]] > > , > > function=[org.opendaylight.openflowplugin.impl.device.initialization. > > OF > > 13DeviceInitializer$$Lambda$1305/1764863356@2d21d4bc]]]], > > function=[org > > .opendaylight.openflowplugin.impl.device.initialization.OF13DeviceIni > > ti > > alizer$$Lambda$1306/930757835@5d94c1b6]]] > > 2018-10-25T05:14:33,047 | WARN | ofppool-11 | > > ContextChainHolderImpl | 379 - > > org.opendaylight.openflowplugin.impl - 0.8.0.SNAPSHOT | This > > mastering > > is mandatory, destroying context chain and closing connection for > > device openflow:185574002334271. > > > > > > _______________________________________________ > > openflowplugin-dev mailing list > > openflowplugin-dev@lists.opendaylight.org > > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev > > > > > _______________________________________________ > openflowplugin-dev mailing list > openflowplugin-dev@lists.opendaylight.org > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev > -- Thanks Anil
_______________________________________________ openflowplugin-dev mailing list openflowplugin-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev