-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Kubelet crashes on concurrent map iteration and map write #124839
Labels
kind/bug
Categorizes issue or PR as related to a bug.
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
k8s-ci-robot
added
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
May 13, 2024
I think the easiest way is to leave the code as-is and guard with an exclusive lock: #124845 |
/sig storage |
k8s-ci-robot
added
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
and removed
needs-sig
Indicates an issue or PR lacks a `sig/foo` label and requires one.
labels
May 13, 2024
/triage accepted |
k8s-ci-robot
added
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
May 13, 2024
Thank you for your reply. I'll think about this solution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
sig/storage
Categorizes an issue or PR as relevant to SIG Storage.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What happened?
When running e2e, the following fatal error can be encountered:
The related code is as follows:
Added read lock on line 634:
kubernetes/pkg/volume/plugins.go
Lines 633 to 666 in a07d3c4
delete map on line 714:
kubernetes/pkg/volume/plugins.go
Lines 694 to 720 in a07d3c4
What did you expect to happen?
What's a good way for the community to solve this problem?
How can we reproduce it (as minimally and precisely as possible)?
None at present
Anything else we need to know?
No response
Kubernetes version
Cloud provider
OS version
Install tools
Container runtime (CRI) and version (if applicable)
Related plugins (CNI, CSI, ...) and versions (if applicable)
The text was updated successfully, but these errors were encountered: