Skip to content
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

bgpv2: use peer asn and address in the key #33263

Merged
merged 1 commit into from
Jun 20, 2024

Conversation

harsimran-pabla
Copy link
Contributor

This change adds the ASN and address to the peer's key along with the name.

Secondly, the order of peer changes is now deleted, updated, and added. This is done because adding an old peer before deleting it will fail when changing the peer ASN or address.

This change also allows setting the local peer port to 0 (random port selection from the kernel). This is required when setting the local port from some value back to 0.

Fixes: #33163

@harsimran-pabla harsimran-pabla requested a review from a team as a code owner June 19, 2024 16:42
@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jun 19, 2024
@harsimran-pabla harsimran-pabla added the release-note/misc This PR makes changes that have no direct user impact. label Jun 19, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jun 19, 2024
@harsimran-pabla harsimran-pabla added dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. area/bgp labels Jun 19, 2024
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jun 19, 2024
@harsimran-pabla
Copy link
Contributor Author

/test

@harsimran-pabla harsimran-pabla added release-note/bug This PR fixes an issue in a previous release of Cilium. release-blocker/1.16 This issue will prevent the release of the next version of Cilium. and removed release-note/misc This PR makes changes that have no direct user impact. labels Jun 19, 2024
Copy link
Contributor

@rastislavs rastislavs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

On updating peer ASN and address, we need to remove old peer and readd
it again. This change adds ASN and address in the key of peer along with
the name.

Secondly, order of changing peer is now delete, update and add. This is
done because adding before deleting old peer is going to fail when
changing ASN.

This change also allows setting local peer port to 0 (random port
selection from kernel)

Signed-off-by: harsimran pabla <hpabla@isovalent.com>
@harsimran-pabla
Copy link
Contributor Author

/test

1 similar comment
@harsimran-pabla
Copy link
Contributor Author

/test

@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jun 19, 2024
@julianwiedmann julianwiedmann added this pull request to the merge queue Jun 20, 2024
Merged via the queue into cilium:main with commit 4775694 Jun 20, 2024
67 checks passed
@joestringer joestringer added the backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. label Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/bgp backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-blocker/1.16 This issue will prevent the release of the next version of Cilium. release-note/bug This PR fixes an issue in a previous release of Cilium.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

BGPv1 and BGPv2 - Updating a peer's ASN has no effect
4 participants