Istio-proxy container failed to start. envoy missing listener for inbound application port

Networking
1

Hi,
I am facing issue in enabling sidecar to my application. envoy container is failed to start with below error.

* failed checking application ports. listeners="0.0.0.0:15090","100.116.0.54:6009","100.69.36.4:9100","100.65.178.245:9001","0.0.0.0:6783","100.64.0.10:53","100.68.58.45:80","100.64.33.155:443","100.66.112.196:443","100.64.33.10:80","100.71.235.250:8080","100.71.146.60:443","100.67.188.95:80","0.0.0.0:9093","100.71.146.60:15031","100.69.140.67:9000","100.71.146.60:15443","100.67.79.143:44134","100.70.237.24:80","100.70.207.183:80","100.69.51.101:80","100.71.146.60:31400","0.0.0.0:9090","0.0.0.0:9300","0.0.0.0:10250","100.65.139.140:26257","0.0.0.0:26257","0.0.0.0:9620","100.71.146.60:15020","100.71.146.60:15029","100.68.106.173:15011","100.64.0.1:443","100.64.201.109:443","100.68.194.144:80","100.71.159.255:7745","100.71.146.60:15030","100.69.5.155:42422","0.0.0.0:443","100.68.13.37:443","100.66.221.179:80","100.70.178.203:80","100.66.53.137:5432","100.71.146.60:15032","100.65.83.255:8099","100.67.188.90:80","0.0.0.0:10055","0.0.0.0:10252","0.0.0.0:10054","0.0.0.0:9480","0.0.0.0:9200","0.0.0.0:8060","0.0.0.0:10251","0.0.0.0:9901","0.0.0.0:9080","0.0.0.0:15014","0.0.0.0:9091","0.0.0.0:80","0.0.0.0:8080","0.0.0.0:15010","0.0.0.0:7002","0.0.0.0:6009","0.0.0.0:15004","0.0.0.0:4001","100.116.0.54:15020","0.0.0.0:15001"
* envoy missing listener for inbound application port: 8004
2019-05-30T08:17:07.179115Z     info    Envoy proxy is NOT ready: 2 errors occurred:

I tried in istio 1.1.3 and 1.1.7 version.

Also the issue is intermittent, in version 1.1.3 I faced sample issue with bookinfo app as well as my application where as in 1.1.7 in bookinfo sidecar started without issue but it is failing for my app.

In different cluster, i see no issue for same version of istio and my application.

Running proxy-status gives below output

NAME                                                  CDS        LDS        EDS               RDS          PILOT                            VERSION
details-v1-68868454f5-smqwr.sample                    SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-57d6f86fb4-rmft6     1.1.3
istio-ingressgateway-d897d9676-wkkj9.istio-system     SYNCED     SYNCED     SYNCED (100%)     NOT SENT     istio-pilot-57d6f86fb4-rmft6     1.1.3
nginx-deployment-67594d6bf6-4wg4j.testing-istio       SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-57d6f86fb4-rmft6     1.1.3
nginx-deployment-67594d6bf6-8dqjn.testing-istio       SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-57d6f86fb4-rmft6     1.1.3
nginx-deployment-67594d6bf6-pqwkp.testing-istio       SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-57d6f86fb4-rmft6     1.1.3
paysafe-psm-sample-latest-5666fdbcfd-xpsms.psm        SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-57d6f86fb4-rmft6     1.1.3
productpage-v1-5cb458d74f-kjp9j.sample                SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-57d6f86fb4-rmft6     1.1.3
ratings-v1-76f4c9765f-d9zf8.sample                    SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-57d6f86fb4-rmft6     1.1.3
reviews-v1-56f6855586-z2trz.sample                    SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-57d6f86fb4-rmft6     1.1.3
reviews-v2-65c9df47f8-b4fdf.sample                    SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-57d6f86fb4-rmft6     1.1.3
reviews-v3-6cf47594fd-tmxxs.sample                    SYNCED     SYNCED     SYNCED (50%)      SYNCED       istio-pilot-57d6f86fb4-rmft6     1.1.3

Though I upgraded to 1.1.7 of istio, the above output still shows 1.1.3 and also 50% means an issue?

Any help to debug this is highly appreciated.

2

I had a similar problem when booting many pods at once: https://github.com/istio/istio/issues/11779

Allegedly this has been fixed in https://github.com/istio/istio/pull/13229 - so you have to wait for 1.1 backport or wait for 1.2 release.

3

Thank you @rvansa. But I am running only one application and then tried bookinfo so in terms of pods its very few like 5 or 6. Do think the issue you mentioned might happened here?

1 Like
4

Also after upgrading istio, proxy-status still shows 1.1.3. Infact I deleted older version (1.1.3) using helm delete and installed 1.1.7. Below Commands I used

helm del istio-init --purge

helm del istio --purge

kubectl get customresourcedefinition -n istio-system | grep 'istio'|awk '{print $1}'|xargs kubectl delete customresourcedefinition -n istio-system

helm repo add istio.io https://storage.googleapis.com/istio-release/releases/1.1.7/charts/

helm repo update

helm install --name istio istio.io/istio-init --namespace istio-system

helm install --name istio istio.io/istio --namespace istio-system

5

We are having the exact same issue with just a single pod. @rvansa do you know if the aforementioned fix only applies if you start multiple pods at the same time or if it is a general fix?

6

i face the same issue in istio v1.2 ,
failed checking application ports.

  • envoy missing listener for inbound application port: 3000
7

Iā€™m having the same problem. Has anyone found a fix for this?

8

Is your pod exposed through a Service?