]> git.puffer.fish Git - mirror/frr.git/commit
tools: fix frr traceback on bgp neighbor bfd deletion 6348/head
authorDon Slice <dslice@cumulusnetworks.com>
Mon, 27 Apr 2020 19:34:08 +0000 (19:34 +0000)
committerDon Slice <dslice@cumulusnetworks.com>
Tue, 5 May 2020 17:59:59 +0000 (17:59 +0000)
commitca7f04961d46b58952dde38d84a7483da53018cc
treec5cdeb90f497c0e9106dd8eb1de5c868c50a96f4
parent44fb33ee585e865345e765143fdada2123875eae
tools: fix frr traceback on bgp neighbor bfd deletion

Problem reported that with certain configs, when the user
deleted a "neighbor x.x.x.x bfd 4 100 100" statement from
frr.conf and then reloaded, a traceback was seen and the
deletion did not succeed.  Found that in some scenarios
it was possible to have something in lines_to_add that
was in a different context and when the re.search was
attempted, it found an empy line and was unhappy.  This
fix avoids trying to search in the wrong context.

Ticket: CM-29145
Signed-off-by: Don Slice <dslice@cumulusnetworks.com>
tools/frr-reload.py