[BGPCEP-600] C: updating example-bgp-rib via openconfig generates exceptions in the log

Blocks — Sun, 3 Mar 2019 11:49:57 +0000

updating the default rib with

PUT /restconf/config/openconfig-network-instance:network-instances/network-instance/global-bgp/openconfig-network-instance:protocols/protocol/openconfig-policy-types:BGP/example-bgp-rib
<protocol xmlns="http://openconfig.net/yang/network-instance">
<name>example-bgp-rib</name>
<identifier xmlns:x="http://openconfig.net/yang/policy-types">x:BGP</identifier>
<bgp xmlns="urn:opendaylight:params:xml:ns:yang:bgp:openconfig-extensions">
<global>
<config>
<router-id>192.0.2.2</router-id>
<as>64496</as>
</config>
<afi-safis>
<afi-safi>
<afi-safi-name xmlns:x="http://openconfig.net/yang/bgp-types">x:IPV4-UNICAST</afi-safi-name>
<receive>true</receive>
<send-max>0</send-max>
</afi-safi>
</afi-safis>
</global>
</bgp>
</protocol>

generates exceptions in the log.

In the https://logs.opendaylight.org/sandbox/jenkins091/bgpcep-csit-1node-userfeatures-only-carbon/2 there is a test case when application peer is configures with routes, bgp peer is configured, then is connected but no routes are advertised.

Robot log here (larger than 1MB, so cannot attach) https://logs.opendaylight.org/sandbox/jenkins091/bgpcep-csit-1node-userfeatures-only-carbon/2/archives/log.html.gz

OpenDaylight JIRA

[BGPCEP-600] C: updating example-bgp-rib via openconfig generates exceptions in the log