istio: panic in istio-init
circleci@default-f18c7071-2f52-4a76-881b-d3468b0cb644:~/tetrate$ kubectl logs httpbin-7d9d5b55b9-5rdlq -n httpbin-middle -c istio-init
Environment:
------------
ENVOY_PORT=
INBOUND_CAPTURE_PORT=
ISTIO_INBOUND_INTERCEPTION_MODE=
ISTIO_INBOUND_TPROXY_MARK=
ISTIO_INBOUND_TPROXY_ROUTE_TABLE=
ISTIO_INBOUND_PORTS=
ISTIO_LOCAL_EXCLUDE_PORTS=
ISTIO_SERVICE_CIDR=
ISTIO_SERVICE_EXCLUDE_CIDR=
Variables:
----------
PROXY_PORT=15001
PROXY_INBOUND_CAPTURE_PORT=15006
PROXY_UID=1337
INBOUND_INTERCEPTION_MODE=REDIRECT
INBOUND_TPROXY_MARK=1337
INBOUND_TPROXY_ROUTE_TABLE=133
INBOUND_PORTS_INCLUDE=*
INBOUND_PORTS_EXCLUDE=15020
OUTBOUND_IP_RANGES_INCLUDE=*
OUTBOUND_IP_RANGES_EXCLUDE=
OUTBOUND_PORTS_EXCLUDE=
KUBEVIRT_INTERFACES=
ENABLE_INBOUND_IPV6=
iptables-restore --noflush /tmp/iptables-rules-1575471817338096531.txt362075769
iptables-restore: line 2 failed
iptables-save
# Generated by iptables-save v1.6.1 on Wed Dec 4 15:03:37 2019
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:ISTIO_INBOUND - [0:0]
:ISTIO_IN_REDIRECT - [0:0]
:ISTIO_OUTPUT - [0:0]
:ISTIO_REDIRECT - [0:0]
-A PREROUTING -p tcp -j ISTIO_INBOUND
-A OUTPUT -p tcp -j ISTIO_OUTPUT
-A ISTIO_INBOUND -p tcp -m tcp --dport 22 -j RETURN
-A ISTIO_INBOUND -p tcp -m tcp --dport 15020 -j RETURN
-A ISTIO_INBOUND -p tcp -j ISTIO_IN_REDIRECT
-A ISTIO_IN_REDIRECT -p tcp -j REDIRECT --to-ports 15006
-A ISTIO_OUTPUT -s 127.0.0.6/32 -o lo -j RETURN
-A ISTIO_OUTPUT ! -d 127.0.0.1/32 -o lo -j ISTIO_IN_REDIRECT
-A ISTIO_OUTPUT -m owner --uid-owner 1337 -j RETURN
-A ISTIO_OUTPUT -m owner --gid-owner 1337 -j RETURN
-A ISTIO_OUTPUT -d 127.0.0.1/32 -j RETURN
-A ISTIO_OUTPUT -j ISTIO_REDIRECT
-A ISTIO_REDIRECT -p tcp -j REDIRECT --to-ports 15001
COMMIT
# Completed on Wed Dec 4 15:03:37 2019
ip6tables-save
panic: exit status 1
goroutine 1 [running]:
istio.io/istio/tools/istio-iptables/pkg/dependencies.(*RealDependencies).RunOrFail(0xd68820, 0x964bef, 0x10, 0xc00000cc80, 0x2, 0x2)
istio.io/istio@v0.0.0/tools/istio-iptables/pkg/dependencies/implementation.go:70 +0x96
istio.io/istio/tools/istio-iptables/pkg/cmd.(*IptablesConfigurator).executeIptablesRestoreCommand(0xc0000edd30, 0x7effa01f7001, 0x0, 0x0)
istio.io/istio@v0.0.0/tools/istio-iptables/pkg/cmd/run.go:484 +0x3aa
istio.io/istio/tools/istio-iptables/pkg/cmd.(*IptablesConfigurator).executeCommands(0xc0000edd30)
istio.io/istio@v0.0.0/tools/istio-iptables/pkg/cmd/run.go:491 +0x42
istio.io/istio/tools/istio-iptables/pkg/cmd.(*IptablesConfigurator).run(0xc0000edd30)
istio.io/istio@v0.0.0/tools/istio-iptables/pkg/cmd/run.go:440 +0x1ace
istio.io/istio/tools/istio-iptables/pkg/cmd.glob..func1(0xd43600, 0xc0000ae900, 0x0, 0x10)
istio.io/istio@v0.0.0/tools/istio-iptables/pkg/cmd/root.go:36 +0xbf
github.com/spf13/cobra.(*Command).execute(0xd43600, 0xc00001e130, 0x10, 0x11, 0xd43600, 0xc00001e130)
github.com/spf13/cobra@v0.0.5/command.go:830 +0x2aa
github.com/spf13/cobra.(*Command).ExecuteC(0xd43600, 0x40574f, 0xc00006a058, 0x0)
github.com/spf13/cobra@v0.0.5/command.go:914 +0x2fb
github.com/spf13/cobra.(*Command).Execute(...)
github.com/spf13/cobra@v0.0.5/command.go:864
istio.io/istio/tools/istio-iptables/pkg/cmd.Execute()
istio.io/istio@v0.0.0/tools/istio-iptables/pkg/cmd/root.go:181 +0x2d
main.main()
github.com/tetrateio/istio@/tools/istio-iptables/main.go:22 +0x20
(ignore the v0.0.0). This is from master branch. When the test is run on a circleci vm. The VM does have ipv6
circleci@default-f18c7071-2f52-4a76-881b-d3468b0cb644:~/tetrate$ ifconfig
docker0 Link encap:Ethernet HWaddr 02:42:00:60:4e:1a
inet addr:172.17.0.1 Bcast:172.17.255.255 Mask:255.255.0.0
inet6 addr: fe80::42:ff:fe60:4e1a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:15948 errors:0 dropped:0 overruns:0 frame:0
TX packets:17185 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1474556 (1.4 MB) TX bytes:9272515 (9.2 MB)
ens4 Link encap:Ethernet HWaddr 42:01:0a:8e:01:e1
inet addr:10.142.1.225 Bcast:10.142.1.225 Mask:255.255.255.255
inet6 addr: fe80::4001:aff:fe8e:1e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1460 Metric:1
RX packets:160543 errors:0 dropped:0 overruns:0 frame:0
TX packets:104259 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2486876849 (2.4 GB) TX bytes:9515959 (9.5 MB)
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 46 (44 by maintainers)
Commits related to this issue
- istio-init: Log iptables rules to help debugging issues GH Issue: https://github.com/istio/istio/issues/19380 — committed to abhide/istio by deleted user 5 years ago
- istio-init: Log iptables rules to help debugging issues (#19436) GH Issue: https://github.com/istio/istio/issues/19380 — committed to istio/istio by abhide 5 years ago
- Do not call ip6tables if IPv6 is disabled Fixes: https://github.com/istio/istio/issues/19380 — committed to istio/istio by rlenglet 5 years ago
- Only run ip6table-save if IPv6 is enabled Fixes: https://github.com/istio/istio/issues/19380 — committed to istio/istio by rlenglet 5 years ago
- Do not configure ip6tables at all if IPv6 is disabled (#19769) * Do not call ip6tables if IPv6 is disabled Fixes: https://github.com/istio/istio/issues/19380 * Remove reference to deleted ./tests/s... — committed to istio/istio by rlenglet 4 years ago
For those who end up in this thread from the google search. I was experiencing the same problem, in my case the failing line number was on the
COMMIT
.It turned out that SELinux was blocking the iptables change. Try to disable the SELinux temporarily by doing
sudo setenforce 0
and then re-run youristioctl kube-inject...
command to verify this is the issue.@rlenglet Similar error in istio-init on GKE. GKE: v1.14.10-gke.24 istio: 1.5.1 (Also I have tested on Istio 1.5.0 and I have got the same issue) NGINX Deployment:
We actually had the exact same issue in Istio/CNI: https://github.com/istio/istio/issues/15895, https://github.com/istio/cni/pull/172. We solved that by just ignoring the errors. But I think these rules are not really required in the first place. I will just remove them.
this is output from successful run
this should be in our init image right? Does not have anything to do with circleci… But something is failing…