concourse: iptables error: Could not fetch rule set generation id: Invalid argument in ubuntu jammy
Summary
After bumping concourse’s base image to ubuntu jammy, k8s-topgun jobs in both dev pipeline and release/6.7.x pipeline are red due to a failed test for dns-proxy set up under containerd runtime.
The error log in worker pod is:
{"timestamp":"2022-09-11T03:41:56.523043712Z","level":"error","source":"worker","message":"worker.garden-runner.logging-runner-exited","data":{"error":"Exit trace for group:\ncontainerd-garden-backend exited with error: setup restricted networks failed: create chain or flush if exists failed: running [/usr/sbin/iptables -t filter -N CONCOURSE-OPERATOR --wait]: exit status 4: iptables v1.8.7 (nf_tables): Could not fetch rule set generation id: Invalid argument\n\n\ncontainerd exited with nil\n","session":"8"}}
Additional context
- Running a local docker (concourse-dev image in ubuntu jammy) with DNS proxy enabled is still working.
- Running a local k8s cluster by minikube (Kubernetes v1.24.3 on Docker 20.10.17), it also works.
- We have been using iptables v1.8.7 since 6.7.3 in ubuntu bionic.
So it might be a specific problem due to GKE cluster 1.24 with containerd based OS image.
We should make sure this bug doesn’t affect concourse bosh release that running on ubuntu jammy stemcell.
Triaging info
- Concourse version:
- Browser (if applicable):
- Did this used to work?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 15 (14 by maintainers)
Commits related to this issue
- Revert "bump concourse chart" as this caused an issue with starting docker see https://github.com/concourse/concourse/issues/8558 This reverts commit 2d7ca7615c145872f84ad4cb531c49ada08f39e8. — committed to cloudfoundry/concourse-infra-for-fiwg by ramonskie 2 years ago
- switch k8s worker to guardian runtime see https://github.com/concourse/concourse/issues/8558 Signed-off-by: Rui Yang <ruiya@vmware.com> — committed to concourse/infrastructure by deleted user 2 years ago
- switch to iptables-legacy there are hosts with newer kernel that throwing error like in this issue https://github.com/concourse/concourse/issues/8558 Signed-off-by: Rui Yang <ruiya@vmware.com> — committed to concourse/concourse-docker by deleted user a year ago
- switch to iptables-legacy there are hosts with newer kernel that throwing error like in this issue https://github.com/concourse/concourse/issues/8558 Signed-off-by: Rui Yang <ruiya@vmware.com> — committed to concourse/concourse-docker by deleted user a year ago
@cortesl for M1 it is a different issue as Concourse binary doesn’t support M1 yet.
i just bumped our concourse from 7.8.1 to 7.8.3 and experience this error as well
when fetching a resource i get the following error msg
seems to me that the worker host as has a newer iptables cli and causes this problem. when searching for this issue it seems that iptables-legacy is suggested for now