-
-
Notifications
You must be signed in to change notification settings - Fork 95
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]: Over-provisioning stops working when one of the PVC is resized #1036
Comments
Debug logs:
|
Same issue is present in Kadalu 1.2.0
|
If the logic in "expansion" should be the same as in "create" then the update_free_size() should't be called for PV_TYPE_SUBVOL even during "expansion", while currently for PV_TYPE_SUBVOL it's not called in "created" and called in "expansion" |
Is it possible to send the PR if the fixes in |
Before doing a PR I guess we have to establish whether Kadalu support over-provisioning for External native mode or not. |
|
Describe the bug
I am using Kadalu 0.9.1 in external native mode, Gluster 10.5, and K3s
I have created a kadalu storage that uses an external gluster volume 29GB
Even if the gluster volume is 29GB I can create 3 PVCs 20GB each, so far the over-provisioning is good:
However, it's pretty odd that
kubectl-kadalu storage-list --status
show no space used a no PVCsI resize one of the PVC and the resize worked (from 20GB to 23GB):
Now
kubectl-kadalu storage-list --status
take into count only the PVC that has been resizedIf I try to create another PVC 20GB it stay pending forever:
The text was updated successfully, but these errors were encountered: