Closed
Description
Bug description
The /usr/local/bin/istio-start.sh
script uses already the go implementation of the iptables but it is missing it in the /usr/local/bin/
dir:
sudo journalctl -fu istio
Dec 16 17:44:50 expand-vm systemd[1]: istio.service: Scheduled restart job, restart counter is at 38.
Dec 16 17:44:50 expand-vm systemd[1]: Stopped istio-sidecar: The Istio sidecar.
Dec 16 17:44:50 expand-vm systemd[1]: Started istio-sidecar: The Istio sidecar.
Dec 16 17:44:50 expand-vm istio-start.sh[4486]: /usr/local/bin/istio-start.sh: line 83: /usr/local/bin/istio-clean-iptables: No such file or directory
Dec 16 17:44:50 expand-vm systemd[1]: istio.service: Main process exited, code=exited, status=127/n/a
Dec 16 17:44:50 expand-vm systemd[1]: istio.service: Failed with result 'exit-code'.
ll /usr/local/bin/
total 130536
drwxr-xr-x 2 root root 4096 Dec 16 17:41 ./
drwxr-xr-x 10 root root 4096 Dec 11 12:40 ../
-rwxr-sr-x 1 root root 56962016 Nov 12 19:04 envoy*
-rwxr-xr-x 1 root root 1917 Nov 12 18:43 istio-clean-iptables.sh*
-rwxr-xr-x 1 root root 22421 Nov 12 18:43 istio-iptables.sh*
-rwxr-xr-x 1 root root 2189 Nov 12 18:43 istio-node-agent-start.sh*
-rwxr-xr-x 1 root root 5072 Nov 12 18:43 istio-start.sh*
-rwxr-xr-x 1 root root 20846069 Nov 12 19:05 node_agent*
-rwxr-sr-x 1 root root 55804760 Nov 12 19:05 pilot-agent*
This means the debian package for the 1.4.2 release can't be used (I check if the error still persist on the master branch)
Expected behavior
All dependencies should be installed.
Steps to reproduce the bug
Install a VM (Ubuntu or Debian) and install the debian package for 1.4.2:
curl -L https://storage.googleapis.com/istio-release/releases/1.4.2/deb/istio-sidecar.deb > istio-sidecar.deb
sudo dpkg -i istio-sidecar.deb
now simply run: sudo /usr/local/bin/istio-start.sh
Version (include the output of istioctl version --remote
and kubectl version
and helm version
if you used Helm)
How was Istio installed?
Environment where bug was observed (cloud vendor, OS, etc)