-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
-
None
When a rogue device (it is not added in whitelist) tries to connect to controller (callhome server), it fails to connect (OK) but the device status "FAILED_NOT_ALLOWED" does not show in the callhome server API (NOK):
GET /restconf/operational/odl-netconf-callhome-server:netconf-callhome-server
404
{"errors":{"error":[{"error-type":"application","error-tag":"data-missing","error-message":"Request could not be completed because the relevant data model content does not exist "}]}}
In the karaf log it can be seen:
2018-10-09T09:34:13,471 | INFO | remote-connector-processing-executor-11 | NetconfDevice | 287 - org.opendaylight.netconf.sal-netconf-connector - 1.8.1.SNAPSHOT | RemoteDevice{netopeer}: Netconf connector initialized successfully
2018-10-09T09:34:13,474 | WARN | opendaylight-cluster-data-notification-dispatcher-48 | CallhomeStatusReporter | 268 - org.opendaylight.netconf.callhome-provider - 1.5.1.SNAPSHOT | No corresponding callhome device found - exiting.
So maybe this is expected behavior.
In any case the failing test has been commented in this patch:
https://git.opendaylight.org/gerrit/#/c/76807
