bug: Use the correct nf_conntrack module depending on kernel #5058
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit fixes an issue where the netfilter conntrack module was hardcoded to the 99-replicated-ipvs.conf section, meaning that after any node restart the possibility exists that the system would try to load the incorrect module if kernel >= 4.18+.
laverya
approved these changes
Feb 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
This commit fixes an issue where the netfilter conntrack module was hardcoded to the 99-replicated-ipvs.conf section, meaning that after any node restart the possibility exists that the system would try to load the incorrect module if kernel >= 4.18+.
Which issue(s) this PR fixes:
Fixes #5057
Special notes for your reviewer:
Steps to reproduce
On a node with kernel version >= 4.18 reload the systemd-modules-load service
Does this PR introduce a user-facing change?
Does this PR require documentation?
NONE