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

iptables: Skip CILIUM_TRANSIENT_FORWARD for IPv6 #14994

Merged
merged 1 commit into from
Feb 17, 2021

Conversation

pchaigno
Copy link
Member

@pchaigno pchaigno commented Feb 16, 2021

Commit 317a671 ("iptables: Populate CILIUM_FORWARD chain for IPv6") fixed the agent to add IPv6 counterparts to the Cilium IPv4 rules in CILIUM_FORWARD. The same method is however used to install rules in CILIUM_FORWARD and CILIUM_TRANSIENT_FORWARD. The IPv6 chain for CILIUM_TRANSIENT_FORWARD doesn't exist, resulting in the following error message:

level=error msg="Command execution failed" cmd="[ip6tables -w 5 -A CILIUM_TRANSIENT_FORWARD -o cilium_host -m comment --comment cilium (transient): any->cluster on cilium_host forward accept -j ACCEPT]" error="exit status 1" subsys=iptables
level=warning msg="ip6tables: No chain/target/match by that name." subsys=iptables
level=warning msg="failed to install transient iptables rules" error="cannot install forward chain rules to CILIUM_TRANSIENT_FORWARD: exit status 1" subsys=datapath-loader

This pull request fixes it by skipping the installation of IPv6 rules in CILIUM_TRANSIENT_FORWARD. If we want those rules, more work is required.

Fixes: #14675

@pchaigno pchaigno added sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages. release-note/misc This PR makes changes that have no direct user impact. needs-backport/1.8 labels Feb 16, 2021
@pchaigno pchaigno requested review from a team and kkourt February 16, 2021 11:51
@maintainer-s-little-helper maintainer-s-little-helper bot added this to In progress in 1.10.0 Feb 16, 2021
@maintainer-s-little-helper maintainer-s-little-helper bot added this to Needs backport from master in 1.9.5 Feb 16, 2021
@maintainer-s-little-helper maintainer-s-little-helper bot added this to Needs backport from master in 1.8.7 Feb 16, 2021
Commit 317a671 ("iptables: Populate CILIUM_FORWARD chain for IPv6")
fixed the agent to add IPv6 counterparts to the Cilium IPv4 rules in
CILIUM_FORWARD. The same method is however used to install rules in
CILIUM_FORWARD and CILIUM_TRANSIENT_FORWARD. The IPv6 chain for
CILIUM_TRANSIENT_FORWARD doesn't exist, resulting in the following
error message:

    level=error msg="Command execution failed" cmd="[ip6tables -w 5 -A CILIUM_TRANSIENT_FORWARD -o cilium_host -m comment --comment cilium (transient): any->cluster on cilium_host forward accept -j ACCEPT]" error="exit status 1" subsys=iptables
    level=warning msg="ip6tables: No chain/target/match by that name." subsys=iptables
    level=warning msg="failed to install transient iptables rules" error="cannot install forward chain rules to CILIUM_TRANSIENT_FORWARD: exit status 1" subsys=datapath-loader

This commit fixes it by skipping the installation of IPv6 rules in
CILIUM_TRANSIENT_FORWARD. If we want those rules, more work is required.

Fixes: 317a671 ("iptables: Populate CILIUM_FORWARD chain for IPv6")
Signed-off-by: Paul Chaignon <paul@cilium.io>
@pchaigno pchaigno force-pushed the pr/pchaigno/fix-error-ip6tables branch from 97fff92 to 5a7ce95 Compare February 16, 2021 14:46
@pchaigno
Copy link
Member Author

test-me-please

@pchaigno pchaigno changed the title iptables: Create CILIUM_TRANSIENT_FORWARD for IPv6 iptables: Skip CILIUM_TRANSIENT_FORWARD for IPv6 Feb 16, 2021
@pchaigno
Copy link
Member Author

Cilium-Ginkgo-GKE failed with known-flake #14996. K8s-1.13-Kernel-netnext failed with known flake #12511. Other jobs are green and the team review is covered. Marking as ready to merge.

@pchaigno pchaigno added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Feb 17, 2021
@jibi jibi merged commit 9d9cc65 into master Feb 17, 2021
1.10.0 automation moved this from In progress to Done Feb 17, 2021
@jibi jibi deleted the pr/pchaigno/fix-error-ip6tables branch February 17, 2021 10:18
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Needs backport from master to Backport pending to v1.9 in 1.9.5 Feb 17, 2021
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Needs backport from master to Backport pending to v1.8 in 1.8.7 Feb 17, 2021
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Backport pending to v1.8 to Backport done to v1.8 in 1.8.7 Feb 17, 2021
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Backport pending to v1.8 to Backport done to v1.8 in 1.8.7 Feb 17, 2021
@maintainer-s-little-helper maintainer-s-little-helper bot moved this from Backport pending to v1.9 to Backport done to v1.9 in 1.9.5 Feb 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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. sig/datapath Impacts bpf/ or low-level forwarding details, including map management and monitor messages.
Projects
No open projects
1.8.7
Backport done to v1.8
1.9.5
Backport done to v1.9
Development

Successfully merging this pull request may close these issues.

None yet

6 participants