New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bgpv1: Set default IdleHoldTime after reset #26001
bgpv1: Set default IdleHoldTime after reset #26001
Conversation
bd07fb8
to
2801bb5
Compare
/test |
2801bb5
to
f742c8c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/test Job 'Cilium-PR-K8s-1.26-kernel-net-next' failed: Click to show.Test Name
Failure Output
Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.26-kernel-net-next/616/ If it is a flake and a GitHub issue doesn't already exist to track it, comment Then please upload the Jenkins artifacts to that issue. |
CI hitting issue similar to #25964
|
test-1.26-net-next failing with known issue : #24514 |
This change sets DefaultIdleHoldTimeAfterReset to 5s, so BGP session move from idle to active state after reset is performed. Default in gobgp is 30s, which is excessively long for session to be re-established. Session reset is performed on some types of neighbor configuration changes, like timers. Signed-off-by: harsimran pabla <hpabla@isovalent.com>
f742c8c
to
84439c8
Compare
/test |
This change sets DefaultIdleHoldTimeAfterReset to 5s, so BGP session moves from idle to active state after reset. The default in gobgp is 30s, which is excessively long for the session to be re-established.
Session reset is performed on neighbor configuration changes, like timers.
Fixes: #25968