-
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
failed to assign quota after kubelet was restarted #124332
Comments
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/sig node |
/remove-sig node |
/sig storage |
cc @pacoxu |
cc @jingxu97 |
What happened?
After kubelet was restarted, kubelet starts to output quota related errors and the total count of entries in
/etc/projects
and/etc/projid
decreased.Similar issues: #115309
What did you expect to happen?
How can we reproduce it (as minimally and precisely as possible)?
tune2fs -O project -Q prjquota /dev/xxx; mount -o prjquota ...
LocalStorageCapacityIsolationFSQuotaMonitoring
in kubelet configAnything 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: