Overview: We configure app-peer and one ibgp. Add 3 routes with app-peer into rib. Start play.py with ibgp-address to initiate connection. Tests whether 3 pre-set routes appear in specific rib for ibgp.

This issue is seen on releng tests in here

Also seen in full rib logs in attachements. Check rib_oxygen_after.log where 127.0.0.2 peer does contain routes, and rib_fluorine_after.log does not. There are no errors in karaf.log

Adding karaf.log from both versions as well, although there are no apparent errors.

Steps to reproduce locally>
1)start bin/karaf (fluorine)
2)run in karaf console

feature:install odl-restconf odl-bgpcep-bgp odl-bgpcep-bgp-config-example

3) go to project integration/test directory, make sure it's up-to-date.
4) switch to directory tools/fastbgp
5)>
run scripts from attachements>
./reconf_safi_all_internal_17900.py
(configures ibgp peer 127.0.0.2 at remote-port 17900)
./conf_app_peer.py
(configures application peer at 127.0.0.1)
./APP_speaker_send.sh
(prefills bgp rib with 3 routes)
./APP_play.sh
(starts bgp peer with play.py)

At this point we should see 3 routes which we send from app peer in rib specific for ibgp with address 127.0.0.2
check full rib at: (particulary peer 127.0.0.2)

curl -H "Accept: application/json" -u admin:admin "http://localhost:8181/restconf/operational/bgp-rib:bgp-rib/rib/example-bgp-rib" | jq "."

also you can check bgp_peer.log which is automatically created after play.sh and should contain information about recieved routes. If failed, there are no information about any routes.
In tests we check for specific line in bgp_peer.log
SUCCESS> INFO BGP-Dummy-1: total_received_nlri_prefix_counter: 3
FAILURE> INFO BGP-Dummy-1: total_received_nlri_prefix_counter: 0

optionally you can than delete the routes with APP_speaker_delete.py to repeat the process.