so this exception says that data store is not available
2016-02-16 17:27:10,945 | WARN | config-pusher |
FlowCapableTopologyProvider | 161 -
org.opendaylight.openflowplugin.applications.topology-manager -
0.2.0.Beryllium | OpenFlow topology read operation failed!
ReadFailedException{message=Error executeRead ReadData for path
/(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=flow:1}],
errorList=[RpcError [message=Error executeRead ReadData for path
/(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)network-topology/topology/topology[{(urn:TBD:params:xml:ns:yang:network-topology?revision=2013-10-21)topology-id=flow:1}],
severity=ERROR, errorType=APPLICATION, tag=operation-failed,
applicationTag=null, info=null,
cause=*org.opendaylight.controller.md.sal.common.api.data.DataStoreUnavailableException:
Shard member-1-shard-topology-operational currently has no leader.*
Try again later.]]}
so looks like cluster didn't come up successfully.
On Tue, Feb 16, 2016 at 1:17 PM, Jamo Luhrsen <[email protected]> wrote:
> you'll have to see what you can discern from the console output:
>
> https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-3node-clustering-only-beryllium/381/consoleFull
>
> when the jobs abort, we don't get the artifacts which are karaf.log for
> csit jobs.
>
> JamO
>
> On 02/16/2016 12:09 PM, Anil Vishnoi wrote:
> > i am trying to get the karaf logs of all the 3 nodes for 381 build, but
> i can't find it. We just keep the logs for
> > latest run ?
> >
> > On Tue, Feb 16, 2016 at 12:04 PM, Anil Vishnoi <[email protected]
> <mailto:[email protected]>> wrote:
> >
> > jamo looking at the above message, it looks like cluster didn't come
> up properly.
> >
> > 381 is the build you see these messages ?
> >
> > On Tue, Feb 16, 2016 at 10:32 AM, Jamo Luhrsen <[email protected]
> <mailto:[email protected]>> wrote:
> >
> > The re-run did not abort:
> >
> >
> https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-3node-clustering-only-beryllium/382/
> >
> > so I know that will probably be good enough to not let this block
> > the release. I still would recommend we try to figure out what
> > happened/broke when it did abort. I will run it a few more times
> > to see if it ever comes back or not.
> >
> > JamO
> >
> > On 02/16/2016 09:53 AM, Jamo Luhrsen wrote:
> > > The latest RC distro didn't come up in our ofp cluster test
> job.
> > >
> > > I saw some deadlockmonitor messages, and then finally a message
> > > about leaders failing to settle after 90 seconds.
> > >
> > > restconf never came up, which is the higher level reason the
> job
> > > aborted.
> > >
> > > I'm re-running it now to see if it's consistent or not. Here
> > > are the two logs I mentioned above:
> > >
> > > 2016-02-16 17:25:19,686 | WARN | saction-51-53'}} |
> DeadlockMonitor | 103 -
> > > org.opendaylight.controller.config-manager - 0.4.0.Beryllium |
> > ModuleIdentifier{factoryName='cluster-admin-provider',
> > > instanceName='cluster-admin-provider'} did not finish after
> 91239 ms
> > > 2016-02-16 17:25:20,175 | ERROR | config-pusher |
> DistributedDataStore | 154 -
> > > org.opendaylight.controller.sal-distributed-datastore -
> 1.3.0.Beryllium | Shared leaders failed to settle in
> > 90 seconds,
> > > giving up
> > >
> > >
> > > Thanks,
> > > JamO
> > >
> > _______________________________________________
> > openflowplugin-dev mailing list
> > [email protected] <mailto:
> [email protected]>
> >
> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
> >
> >
> >
> >
> > --
> > Thanks
> > Anil
> >
> >
> >
> >
> > --
> > Thanks
> > Anil
>
--
Thanks
Anil
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
