Build #17

FreeRangeRouting Protocol Suite

Build result summary

Details

Completed
Duration
97 minutes
Labels
version=frr-7_1-dev-2529-gbb4eca5cbgit=https_//github_com/frrouting/frr_gitbuildurl=https_//ci1_netdef_org/browse/frr-frr46-17branch=dev/7_2
Revision
bb4eca5cb29f3b66f38c4996ddf96b613a6925b0 bb4eca5cb29f3b66f38c4996ddf96b613a6925b0
Total tests
7647
Fixed in
#18 (Changes by Donald Sharp and Donatas Abraitis <donatas.abraitis@gmail.com>)
No failed tests found, a possible compilation error occurred.

Tests

Responsible

No one has taken responsibility for this failure

Code commits

Author Commit Message Commit date
Donatas Abraitis <donatas.abraitis@gmail.com> Donatas Abraitis <donatas.abraitis@gmail.com> bb4eca5cb29f3b66f38c4996ddf96b613a6925b0 bb4eca5cb29f3b66f38c4996ddf96b613a6925b0 Merge pull request #5057 from dslicenc/bgp-next-hop-routemap-72
7.2: bgpd: stop sending nexthop set by "route-map in" to eBGP peers
Don Slice <dslice@cumulusnetworks.com> Don Slice <dslice@cumulusnetworks.com> 12a956c42a6557f852348c7df2a197e833272c79 m 12a956c42a6557f852348c7df2a197e833272c79 bgpd: stop sending nexthop set by "route-map in" to eBGP peers
Problem reported that when a "neighbor x.x.x.x route-map FOO in"
set a next-hop value, that modified next-hop value was also sent
to eBGP peers.  This is incorrect since bgp is expected to set
next-hop to self when sending to eBGP peers unless third party
next-hop on a shared segment is true.  This fix modifies the
behavior to stop sending the modified next-hop to eBGP peers
if the route-map was applied inbound on another peer.

Ticket: CM-26025
Signed-off-by: Don Slice <dslice@cumulusnetworks.com>

Error summary for Ubuntu 18.04 ARM8 build

The job generated some errors, drill down into the full build log for more details.

ERROR: Installation Error during libyang Package installation - retry in 60s
ERROR: Installation Error during libyang Package installation again