bgpd: Request SRv6 locator after zebra connection (backport #18069) #18115
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.
When SRv6 is enabled and an SRv6 locator is specified in the BGP configuration, BGP may attempt to request SRv6 locator information from zebra before the connection is fully established. If this occurs, the request fails with the following error:
As a result, BGP is unable to obtain the locator information, preventing SRv6 VPN from working.
This PR fixes the issue by ensuring BGP requests SRv6 locator information once the connection with zebra is successfully established.
This PR fixes intermittent failures in BGP SRv6 L3VPN topotests.
This is an automatic backport of pull request #18069 done by Mergify.