Build #2,096

FreeRangeRouting Protocol Suite

Build: #2096 was successful Changes by Russ White <russ@riw.us>

Build result summary

Details

Completed
Duration
128 minutes
Labels
version=frr-7_1-dev-846-g0697abef9git=https_//github_com/frrouting/frr_gitbuildurl=https_//ci1_netdef_org/browse/frr-frr-2096branch=master
Revision
0697abef9d425e0443a6746021ed012eed3cfd13 0697abef9d425e0443a6746021ed012eed3cfd13
Total tests
6651
First to pass since
#2095 (Changes by Russ White <russ@riw.us>)

Tests

Code commits

Author Commit Message Commit date
Russ White <russ@riw.us> Russ White <russ@riw.us> 0697abef9d425e0443a6746021ed012eed3cfd13 0697abef9d425e0443a6746021ed012eed3cfd13 Merge pull request #4096 from donaldsharp/pim_nht_cleanup
Pim nht cleanup
Donald Sharp Donald Sharp 2cb7234faff0ac0c0b51cb4c0585d0500bb48f7e m 2cb7234faff0ac0c0b51cb4c0585d0500bb48f7e pimd: Add a flag PIM_NEXTHOP_ANSWER_RECEIVED
Track whether or not we have received an answer from
our query to do nexthop tracking.  This allows us to
go straight to doing a synchronous query for our
RPF.

Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Donald Sharp Donald Sharp 2ccc414b19c9c2115fae5b2c36c69b480b7cfcd9 m 2ccc414b19c9c2115fae5b2c36c69b480b7cfcd9 pimd: Zero out nhop being used
Zero out the lookup nexthop for usage, prevent a crash.

Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Donald Sharp Donald Sharp 2de05c606e34e8ea2bb60fce110228caeb356e48 m 2de05c606e34e8ea2bb60fce110228caeb356e48 pimd: Initiate *,G S,G RPT Prune in some cases
On the LHR after we decide that traffic is flowing and
we set the SPT bit for the S,G *and* the incoming IIF
of the S,G is different than the incoming IIF of the *,G
we should immediately send the *,G S,G RPT Prune as
a triggered response instead of waiting for the next
cycle.

Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Donald Sharp Donald Sharp 5bd51314352b25420ef1c8df7265b95cdad88e37 m 5bd51314352b25420ef1c8df7265b95cdad88e37 pimd: Determining if we are the RP should happen always
When creating new RP information from a `ip pim rp A.B.C.D/M A.B.C.D`
we should determine if we are the RP even if we can or cannot
determine if we have a path to the RP via RPF.

This is because we should determine if we are the RP based upon a
connected ip address match not whether or not we have a path to
the RPF.  We would normally think this is not important but
RPF is inherently asynchronous and we can have a state where
we have registered for nht but have not received the actual
path back yet from zebra.

Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>

Tests

Fixed tests 3
Status Test Failing since View job Duration
Successful test_bfd_topo2 test_protocols_convergence History
Failing since build #2095 (Changes by Russ White <russ@riw.us>) Topology Tests on Ubuntu 16.04 amd64 1 min
Successful test_bfd_topo2 test_protocols_convergence History
Failing since build #2095 (Changes by Russ White <russ@riw.us>) Topology Tests on Ubuntu 16.04 arm8 1 min
Successful test_bgp_l3vpn_to_bgp_direct test_adjacencies History
Failing since build #2095 (Changes by Russ White <russ@riw.us>) Topology Tests on Ubuntu 18.04 amd64 1 min