Reenable IPv6 BGP neighbor check during warm-reboot #8937
Merged
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.
Description of PR
Summary:
Fixes # (issue)
Now that sonic-net/sonic-buildimage#15688 has been merged, re-enable checking the IPv6 BGP neighbor status during a warm-reboot.
This reverts #8735 and #8746.
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Did a warm-reboot on virtual switch, and verified that it passed.
One oddity that was noticed was that the IPv6 BGP appears to have gone down for about 23 seconds, whereas IPv4 BGP did not go down. This wasn't treated as a failure, though.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation