Add BFD peer awareness to frr-reload.py and vtysh markfile #6708
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a bugfix for #6511.
frr-reload.py is amended to recognize the peer sub-context in the BFD configuration node. Without this change, it erroneously treats everything under BFD as a single context as shown in this snippet from frr-reload.log
With the included change, the peer is properly handled as a sub-context, and the peer config is handled properly.
vtysh.c is amended to also recognize the peer sub-context in the BFD configuration node. Without this change, vtysh -m will not mark the exit of a peer and actually writes an end before the subsequent peers are processed. Without the exit in place for the peer, frr-reload.py will not recognize the need to pop up 1 context level. Here is vtysh -m without the change...
here is the output with the included patch.