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

v1.16 Backports 2024-11-21 #36093

Merged
merged 2 commits into from
Nov 28, 2024
Merged

v1.16 Backports 2024-11-21 #36093

merged 2 commits into from
Nov 28, 2024

Conversation

pippolo84
Copy link
Member

@pippolo84 pippolo84 commented Nov 21, 2024

Once this PR is merged, a GitHub action will update the labels of these PRs:

 35144

Sorry, something went wrong.

@pippolo84 pippolo84 added kind/backports This PR provides functionality previously merged into master. backport/1.16 This PR represents a backport for Cilium 1.16.x of a PR that was merged to main. labels Nov 21, 2024
@pippolo84 pippolo84 force-pushed the pr/v1.16-backport-2024-11-21-12-48 branch from c4c8ae8 to ba2b78b Compare November 21, 2024 11:50
@pippolo84
Copy link
Member Author

/test-backport-1.16

@asauber
Copy link
Member

asauber commented Nov 21, 2024

This is hitting #36086 in CI

@pippolo84
Copy link
Member Author

The only (required) test failing (ci-ipsec-upgrade) is hitting #36086, so marking this ready to merge.

@pippolo84 pippolo84 added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Nov 22, 2024
@tklauser tklauser enabled auto-merge November 27, 2024 12:54
@julianwiedmann
Copy link
Member

I think the right call here is rebasing to pick up the fix, and re-run CI.

[ upstream commit 658382a ]

Add AllMatch function that returns true if the predicate evaluates to
true for each element in the slice.

Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
[ upstream commit 7e6195b ]

When a new node is discovered, in case of a multi-devices environment,
we loop over each neighbor discovery link to found the next hop IP for
the given node. For each link, if a next hop is found, it is inserted in
the related neighNextHopByNode4 map.

In this setup, it is possible that a node is reachable only by a subset
of the neighbor discovery links. This case should not be considered an
error, as long as the node is reachable by at least one link. Therefore,
the errors handling logic is changed to propagate an error only when it
is not possible to find a next hop for any link.

This also reduces the amount of memory used for joining all the strings
related to the false error condition described above, besides reducing
the amount of useless retry runs of the node-neighbor-link-updater
controller.

Fixes: #34020

Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
@julianwiedmann julianwiedmann force-pushed the pr/v1.16-backport-2024-11-21-12-48 branch from ba2b78b to d8ee97a Compare November 28, 2024 07:27
@julianwiedmann julianwiedmann removed the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Nov 28, 2024
@julianwiedmann
Copy link
Member

/test-backport-1.16

@tklauser tklauser added this pull request to the merge queue Nov 28, 2024
@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 Nov 28, 2024
Merged via the queue into v1.16 with commit 71cfa37 Nov 28, 2024
297 of 310 checks passed
@tklauser tklauser deleted the pr/v1.16-backport-2024-11-21-12-48 branch November 28, 2024 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/1.16 This PR represents a backport for Cilium 1.16.x of a PR that was merged to main. kind/backports This PR provides functionality previously merged into master. ready-to-merge This PR has passed all tests and received consensus from code owners to merge.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants