[CONTROLLER-1383] NullPointer when building Topology data for netconf node when Host Name fails to resolve Created: 26/Jun/15  Updated: 22/Jul/15  Resolved: 22/Jul/15

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

Type: Bug
Reporter: Wojciech Dec Assignee: Maros Marsalek
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Attachments: File controller.currentconfig.xml     Text File karaf.log    
External issue ID: 3878

 Description   

With the following config file present in etc/opendaylight/current/ ODL is unable to startup ; hangs at the point shown in the logs and throws countless errors about missing models:

Exception in thread "config-pusher" java.lang.IllegalStateException: Unable to push configuration due to missing yang models. Required yang models that are missing: [urn:opendaylight:params:xml:ns:yang:controller:config:netconf:client:dispatcher?module=odl-netconfig-client-cfg&revision=2014-04-08, urn:opendaylight:params:xml:ns:yang:controller:config:netconf?module=odl-netconf-cfg&revision=2014-04-08, urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector-cfg&revision=2013-10-28]

Problem is readily reproducible.

Removing the config file and reloading allows the controller to start up.

 Comments   
Comment by Wojciech Dec [ 26/Jun/15 ]

Attachment controller.currentconfig.xml has been added with description: config file

Comment by Wojciech Dec [ 26/Jun/15 ]

Attachment karaf.log has been added with description: log

Comment by Wojciech Dec [ 26/Jun/15 ]

Running:

http://nexus.opendaylight.org/service/local/artifact/maven/redirect?r=opendaylight.release&g=org.opendaylight.integration&a=distribution-karaf&v=0.3.0-Lithium&e=zip

Note: External symptom, when accessing controller via restconf is:
{"error":"Authentication service unavailable"

Comment by Tomas Cere [ 10/Jul/15 ]

This happens because of a NullPointer from an InetSocketAddress.getAddress() call when the host name fails to resolve, workaround for now is to use ip instead of host name.

Comment by Maros Marsalek [ 14/Jul/15 ]

https://git.opendaylight.org/gerrit/#/c/24095/1

This is also present on master.

Generated at Wed Feb 07 19:55:24 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.