-
Notifications
You must be signed in to change notification settings - Fork 308
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
[BUG] ContainerD deadlock present in 1.7.15, fixed in 1.7.17 or newer #4426
Comments
We are working on bumping the containerd version to |
We now have a new node image version releasing which has containerd 1.7.20. The node image version with updated containerd is |
Thank you we are testing the fixes now. FYI we also tested the azure linux image which has containerd 1.6.20 and that also has a deadlock bug fixed in 1.6.25 Edit: Actually azure linux latest images has containerd 1.6.26 so we are continuing to test with azurelinux. |
Unfortunately it looks like deadlock issue is still happening for us even with the new version of containerd. We will continue investigating |
Describe the bug
We are seeing our AKS nodes running 1,29.5 go into a not ready state and looking at logs it appears that containerd is hanging and becoming non responsive.
There are 2 deadlock bugs fixed in containerd 1.7.16 and 1.7.17
containerd/ttrpc#168
containerd/nri#79
When can we expect containerd to be upgraded to 1.7.17 or newer to address these deadlock issues?
To Reproduce
We are seeing this issue most reliably when we enable istio native sidecars [https://learn.microsoft.com/en-us/azure/aks/istio-native-sidecar] on our test cluster where we have a large number of cron jobs running to execute various tests. This is blocking us from adopting istio native sidecars in any production environments.
Expected behavior
Our cluster nodes remain in a ready state
Screenshots
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: