Skip to content
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

Failed to initialize key-value store of network plugin: error Acquiring store lock: timed out locking store #2692

Closed
tamilmani1989 opened this issue Apr 17, 2024 · 2 comments
Assignees
Labels
stale Stale due to inactivity.

Comments

@tamilmani1989
Copy link
Member

tamilmani1989 commented Apr 17, 2024

What happened:

Issue:
Pod creation in AKS cluster fails with CNI error. This error happens if CNI acquires the lock and stuck in some call and not releasing the lock to another cni process. Upon investigation, found iptable list cmd in CNI taking longer time (around 2 to 3 mins) to respond. Iptables list cmd tries to do reverse dns lookup for IPAddresses present in the chain. Customer configured to use custom dns server in AKS and this custom dns server taking long to respond and thus causing CNI executing IPTable cmd to return after 2 mins and other CNI processes waiting for lock couldn't acquire it and resulting in this error.

Impact:
This affects customer who uses Azure CNI/Azure CNI Powered by Cilium pod subnet cluster and configured custom dns server and only if custom dns server is either not reponding or taking longer to respond.

Fix
CNI can prevent iptables list cmd to do reverse dns lookup and just display in numeric by running with
-n option. PR for the fix: #2682

Impacted CNI Versions: 1.4.x, 1.5.x

Orchestrator and Version (e.g. Kubernetes, Docker):
Kubernetes

Operating System (Linux/Windows):
Linux

Kernel (e.g. uanme -a for Linux or $(Get-ItemProperty -Path "C:\windows\system32\hal.dll").VersionInfo.FileVersion for Windows):
5.15

Anything else we need to know?:
[Miscellaneous information that will assist in solving the issue.]

@tamilmani1989 tamilmani1989 self-assigned this Apr 17, 2024
Copy link

github-actions bot commented May 2, 2024

This issue is stale because it has been open for 2 weeks with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale due to inactivity. label May 2, 2024
Copy link

github-actions bot commented May 9, 2024

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Stale due to inactivity.
Projects
None yet
Development

No branches or pull requests

1 participant