[NETCONF-378] Initialization in sal failed, disconnecting from device Created: 21/Mar/17  Updated: 15/Mar/19  Resolved: 28/Apr/17

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Claudio David Gasparini Assignee: Miroslav Kovac
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Issue Links:
Duplicate
is duplicated by NETCONF-391 Initialization in sal failed, disconn... Resolved
External issue ID: 8032

 Description   

Seen under bgpcep-csit-3node-periodic-bgpclustering-only-carbon/

temporal logs

https://logs.opendaylight.org/sandbox/jenkins091/bgpcep-csit-3node-periodic-bgpclustering-only-carbon/5/archives/odl2_karaf.log.gz

2017-03-21 07:46:18,764 | ERROR | sing-executor-11 | NetconfDevice | 342 - org.opendaylight.netconf.sal-netconf-connector - 1.5.0.SNAPSHOT | RemoteDevice

{test-device}

: Initialization in sal failed, disconnecting from device
java.lang.NullPointerException: Closed
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:226)[84:com.google.guava:18.0.0]
at org.opendaylight.netconf.sal.connect.netconf.sal.NetconfDeviceSalProvider$MountInstance.onTopologyDeviceConnected(NetconfDeviceSalProvider.java:135)[342:org.opendaylight.netconf.sal-netconf-connector:1.5.0.SNAPSHOT]
at org.opendaylight.netconf.topology.singleton.impl.MasterSalFacade.registerMasterMountPoint(MasterSalFacade.java:150)[345:org.opendaylight.netconf.topology-singleton:1.2.0.SNAPSHOT]
at org.opendaylight.netconf.topology.singleton.impl.MasterSalFacade.onDeviceConnected(MasterSalFacade.java:91)[345:org.opendaylight.netconf.topology-singleton:1.2.0.SNAPSHOT]
at org.opendaylight.netconf.topology.singleton.impl.MasterSalFacade.onDeviceConnected(MasterSalFacade.java:44)[345:org.opendaylight.netconf.topology-singleton:1.2.0.SNAPSHOT]
at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice.handleSalInitializationSuccess(NetconfDevice.java:213)[342:org.opendaylight.netconf.sal-netconf-connector:1.5.0.SNAPSHOT]
at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice$SchemaSetup.setUpSchema(NetconfDevice.java:461)[342:org.opendaylight.netconf.sal-netconf-connector:1.5.0.SNAPSHOT]
at org.opendaylight.netconf.sal.connect.netconf.NetconfDevice$SchemaSetup.run(NetconfDevice.java:426)[342:org.opendaylight.netconf.sal-netconf-connector:1.5.0.SNAPSHOT]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_121]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]

 Comments   
Comment by Miroslav Kovac [ 05/Apr/17 ]

https://git.opendaylight.org/gerrit/#/c/54310/

Comment by Miroslav Kovac [ 24/Apr/17 ]

It seemes to be a problem only because it is logged as an error. When I compared times in suit and karaf logs in which error appears, it doesn`t cause any robot test to fail in that suit (020 Singlepeer Prefixcount 100Kroutes [1]).

This error should appear when new master is assigned while old one is still creating a mountpoint and therefore DOMMountPointService is set to null

[1] https://jenkins.opendaylight.org/releng/view/bgpcep/job/bgpcep-csit-3node-periodic-bgpclustering-only-carbon/236/robot/report/log.html

Comment by Miroslav Kovac [ 26/Apr/17 ]

git fetch ssh://miroslav.kovac@git.opendaylight.org:29418/netconf refs/changes/74/54874/3 && git checkout FETCH_HEAD

Comment by Miroslav Kovac [ 26/Apr/17 ]

(In reply to Miroslav Kovac from comment #4)
> git fetch ssh://miroslav.kovac@git.opendaylight.org:29418/netconf
> refs/changes/74/54874/3 && git checkout FETCH_HEAD

carbon version

Comment by Miroslav Kovac [ 26/Apr/17 ]

sorry it should have been this one. carbon version ->
https://git.opendaylight.org/gerrit/#/c/54874/

Generated at Wed Feb 07 20:14:51 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.