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
istio side car proxy Version istio/proxyv2:1.15.3 is crashing #50952
Comments
i have pasted the error logs above, failing to understand what could be the reason, i tried rolling restart of the istiod deployment, didnt help. seeing the same error logs as above in istiod pod logs as well |
1.15 was EOL for a long long time, please upgrade and retest. |
@zirain thanks for responding, i do agree, we have to upgrade, do we have any solution for this problem, as we are currently using the same version in prod, it would take us a week to upgrade to new version until we push it prod |
|
can you please help me, which configuration to verify, i'm currently blocked, istio is only being used as a proxy and other features are currenlty not in use on these clusters |
apiVersion: install.istio.io/v1alpha1 |
Exec lifecycle hook ([pilot-agent wait]) for Container "istio-proxy" in Pod "cache-7b6b-cb57t_next(852fb1c9-93db-78169afce051)" failed - error: command 'pilot-agent wait' exited with 255: Error: timeout waiting for Envoy proxy to become ready. Last error: HTTP status code 503... |
I think I saw this in the past, I recall it was from some invalid config that had port unset and missed validation. |
thanks for responding @howardjohn , we are in process to migrate, since this is currently in prod, we are trying to mitigate this issue, can you please share more info when you say invalid config that had port unset. which config are you referring here, can you please elaborate, thanks |
I think it was a Gateway but not sure, and that wouldn't apply here. It was at a previous company so I don't have access to more info. I recall it was for using an old version though TBH and the issue has been fixed already |
Do you have any EnvoyFilters recently changed that may break that? |
Is this the right place to submit this?
Bug Description
we are using istio sidecar for all our workloads, we havent faces any problem but since yesterday, the envoy proxy has crashed and hence the app is unavailable. however, the proxy version on other clusters are working fine.
Version
Additional Information
2024-05-09T05:28:36.469821Z warning envoy config gRPC config for type.googleapis.com/envoy.config.listener.v3.Listener rejected: Error adding/updating listener(s) 0.0.0.0_0: cannot bind '0.0.0.0': Read-only file system
99
98
2024-05-09T05:28:36.497922Z warn Envoy proxy is NOT ready: config received from XDS server, but was rejected: cds updates: 15 successful, 0 rejected; lds updates: 0 successful, 15 rejected
97
2024-05-09T05:28:37.012659Z warn Envoy proxy is NOT ready: config received from XDS server, but was rejected: cds updates: 16 successful, 0 rejected; lds updates: 0 successful, 15 rejected
96
2024-05-09T05:28:37.115585Z error envoy config listener '0.0.0.0_0' failed to bind or apply socket options: cannot bind '0.0.0.0': Read-only file system
95
2024-05-09T05:28:37.185936Z warning envoy config gRPC config for type.googleapis.com/envoy.config.listener.v3.Listener rejected: Error adding/updating listener(s) 0.0.0.0_0: cannot bind '0.0.0.0': Read-only file system
94
93
2024-05-09T05:28:37.296195Z error envoy config listener '0.0.0.0_0' failed to bind or apply socket options: cannot bind '0.0.0.0': Read-only file system
The text was updated successfully, but these errors were encountered: