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

daemon: ignore EEXIST on NodeEnsureLocalIPRule #24645

Merged
merged 1 commit into from Mar 30, 2023

Conversation

tklauser
Copy link
Member

According to Nik, some Kernel versions (namely 4.9 which is still supported in v1.13) doesn't support the fib rule protocol attribute. The call fails with the following error:

daemon creation failed: error while initializing daemon: failed to ensure local IP rules: could not replace IPv4 local rule: file exists"

See #24607 (comment)

In order to ease backporting, let's also apply this change on master even though 4.9 is no longer supported (ref. #22116). The EEXIST case should not occur on kernels which support the fib rule protocol attribute.

Fixes: 291852a ("datapath/linux: make sure we have a local rule with proto kernel")

According to Nik, some Kernel versions (namely 4.9 which is still
supported in v1.13) doesn't support the fib rule protocol attribute.
The call fails with the following error:

    daemon creation failed: error while initializing daemon: failed to ensure local IP rules: could not replace IPv4 local rule: file exists"

See #24607 (comment)

In order to ease backporting, let's also apply this change on master
even though 4.9 is no longer supported (ref. #22116). The EEXIST case
should not occur on kernels which support the fib rule protocol
attribute.

Fixes: 291852a ("datapath/linux: make sure we have a local rule with proto kernel")
Suggested-by: Nikolay Aleksandrov <nikolay@isovalent.com>
Co-authored-by: Nikolay Aleksandrov <nikolay@isovalent.com>
Signed-off-by: Tobias Klauser <tobias@cilium.io>
@tklauser tklauser added release-note/misc This PR makes changes that have no direct user impact. affects/v1.11 This issue affects v1.11 branch affects/v1.12 This issue affects v1.12 branch needs-backport/1.13 This PR / issue needs backporting to the v1.13 branch affects/v1.13 This issue affects v1.13 branch labels Mar 30, 2023
@tklauser tklauser requested a review from a team as a code owner March 30, 2023 08:42
@tklauser tklauser requested a review from pippolo84 March 30, 2023 08:42
@maintainer-s-little-helper maintainer-s-little-helper bot added this to Needs backport from master in 1.13.2 Mar 30, 2023
@tklauser
Copy link
Member Author

tklauser commented Mar 30, 2023

/test

Job 'Cilium-PR-K8s-1.24-kernel-5.4' failed:

Click to show.

Test Name

K8sDatapathConfig Encapsulation Check iptables masquerading with random-fully

Failure Output

FAIL: Pod "testclient-49hkx" can not connect to "http://google.com"

If it is a flake and a GitHub issue doesn't already exist to track it, comment /mlh new-flake Cilium-PR-K8s-1.24-kernel-5.4 so I can create one.

@tklauser tklauser mentioned this pull request Mar 30, 2023
9 tasks
@tklauser
Copy link
Member Author

tklauser commented Mar 30, 2023

@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 Mar 30, 2023
@tklauser tklauser merged commit 0cb19ef into master Mar 30, 2023
43 checks passed
@tklauser tklauser deleted the pr/tklauser/fix-ip-rules-eexist branch March 30, 2023 12:41
@tklauser tklauser added backport-pending/1.13 The backport for Cilium 1.13.x for this PR is in progress. and removed needs-backport/1.13 This PR / issue needs backporting to the v1.13 branch labels Mar 30, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Needs backport from master to Backport pending to v1.13 in 1.13.2 Mar 30, 2023
@tklauser tklauser added needs-backport/1.13 This PR / issue needs backporting to the v1.13 branch and removed backport-pending/1.13 The backport for Cilium 1.13.x for this PR is in progress. labels Mar 30, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Backport pending to v1.13 to Needs backport from master in 1.13.2 Mar 30, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Backport pending to v1.13 to Needs backport from master in 1.13.2 Mar 30, 2023
@jibi jibi removed affects/v1.11 This issue affects v1.11 branch affects/v1.12 This issue affects v1.12 branch needs-backport/1.13 This PR / issue needs backporting to the v1.13 branch affects/v1.13 This issue affects v1.13 branch labels Apr 3, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot removed this from Needs backport from master in 1.13.2 Apr 3, 2023
@jibi
Copy link
Member

jibi commented Apr 3, 2023

Dropping the backporting labels as the PR it fixes has been reverted #24288

@jibi jibi mentioned this pull request Apr 3, 2023
11 tasks
@jibi jibi added affects/v1.11 This issue affects v1.11 branch affects/v1.12 This issue affects v1.12 branch needs-backport/1.13 This PR / issue needs backporting to the v1.13 branch backport/author The backport will be carried out by the author of the PR. labels Apr 5, 2023
@julianwiedmann
Copy link
Member

According to Nik, some Kernel versions (namely 4.9 which is still supported in v1.13)

For v1.13 we now require a kernel >= 4.19, thus dropping the backport label.

@julianwiedmann julianwiedmann removed the needs-backport/1.13 This PR / issue needs backporting to the v1.13 branch label Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects/v1.11 This issue affects v1.11 branch affects/v1.12 This issue affects v1.12 branch backport/author The backport will be carried out by the author of the PR. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants