Re: [release] [OpenDaylight TSC] Neon MRI CSITs
Luis Gomez
For netconf, I see 2 problems:
toggle quoted message
Show quoted text
1) Issue installing the call home bundle: 2018-10-19T11:30:44,285 | ERROR | Blueprint Extender: 2 | NetconfCallHomeServer | 279 - org.opendaylight.netconf.callhome-protocol - 1.6.0.SNAPSHOT | Unable to start NETCONF CallHome Service java.io.IOException: java.lang.IllegalStateException: incompatible event loop type: io.netty.channel.DefaultEventLoop See full exception in: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/netconf-csit-1node-callhome-only-neon/73/odl_1/odl1_karaf.log.gz 2) Impact on the RESTCONF to NETCONF performance test: REST client tool gets timeout reading device config: 12:14:18.927 [pool-4-thread-1] WARN o.o.n.t.t.c.h.p.SyncExecutionStrategy - Failed to execute request java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException: Read timeout to /10.30.170.124:8181 of 60000 ms at com.ning.http.client.providers.netty.future.NettyResponseFuture.abort(NettyResponseFuture.java:231) at com.ning.http.client.providers.netty.request.NettyRequestSender.abort(NettyRequestSender.java:422) at com.ning.http.client.providers.netty.request.timeout.TimeoutTimerTask.expire(TimeoutTimerTask.java:47) at com.ning.http.client.providers.netty.request.timeout.ReadTimeoutTimerTask.run(ReadTimeoutTimerTask.java:57) at org.jboss.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:556) at org.jboss.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:632) at org.jboss.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:369) at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at java.lang.Thread.run(Thread.java:748) Caused by: java.util.concurrent.TimeoutException: Read timeout to /10.30.170.124:8181 of 60000 ms See full test in: https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-1node-scale-only-neon BR/Luis On Oct 19, 2018, at 12:02 PM, Luis Gomez <ecelgp@...> wrote: |
|