-
Notifications
You must be signed in to change notification settings - Fork 63
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
When docker overlay2.size is enabled, the actual size of the pvc request is always the overlay2.size setting size #176
Comments
I notice that overwriting hostpathClass.name from openebs-hostpath to local-ssd will trigger this problem, as described in helm chart values. You must redeploy openebs without modifying hostpathClass.name to work properly |
I should have followed the tutorial to create a new storageClass instead of renaming openebs-hostpath |
The use of quota on the worker node is set correctly, but setting quota on the master node is still equivalent to docker overlay.size The master and the worker nodes with different, the master node has taint Create a size 50GB pvc, the localpv logs: I0330 09:27:25.421180 1 controller.go:1366] provision "default/localpv-vol" class "openebs-hostpath": started
I0330 09:27:25.427411 1 event.go:285] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"localpv-vol", UID:"d6b4589f-1c60-449f-9a62-dba6849d09a7", APIVersion:"v1", ResourceVersion:"11873609", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "default/localpv-vol"
I0330 09:27:25.429837 1 provisioner_hostpath.go:77] Creating volume pvc-d6b4589f-1c60-449f-9a62-dba6849d09a7 at node with labels {map[kubernetes.io/hostname:mn03.zw1.local]}, path:/var/openebs/local/pvc-d6b4589f-1c60-449f-9a62-dba6849d09a7,ImagePullSecrets:[]
2024-03-30T09:27:31.477Z INFO app/provisioner_hostpath.go:131 {"eventcode": "local.pv.quota.success", "msg": "Successfully applied quota", "rname": "pvc-d6b4589f-1c60-449f-9a62-dba6849d09a7", "storagetype": "hostpath"}
2024-03-30T09:27:31.478Z INFO app/provisioner_hostpath.go:215 {"eventcode": "local.pv.provision.success", "msg": "Successfully provisioned Local PV", "rname": "pvc-d6b4589f-1c60-449f-9a62-dba6849d09a7", "storagetype": "hostpath"}
I0330 09:27:31.478134 1 controller.go:1449] provision "default/localpv-vol" class "openebs-hostpath": volume "pvc-d6b4589f-1c60-449f-9a62-dba6849d09a7" provisioned
I0330 09:27:31.478150 1 controller.go:1462] provision "default/localpv-vol" class "openebs-hostpath": succeeded
I0330 09:27:31.478162 1 volume_store.go:212] Trying to save persistentvolume "pvc-d6b4589f-1c60-449f-9a62-dba6849d09a7"
I0330 09:27:31.481748 1 volume_store.go:219] persistentvolume "pvc-d6b4589f-1c60-449f-9a62-dba6849d09a7" saved
I0330 09:27:31.481862 1 event.go:285] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"localpv-vol", UID:"d6b4589f-1c60-449f-9a62-dba6849d09a7", APIVersion:"v1", ResourceVersion:"11873609", FieldPath:""}): type: 'Normal' reason: 'ProvisioningSucceeded' Successfully provisioned volume pvc-d6b4589f-1c60-449f-9a62-dba6849d09a7 |
dynamic-localpv-provisioner/cmd/provisioner-localpv/app/helper_hostpath.go Lines 292 to 293 in 2f165df
Generating a project id based on the above code may cause docker to compete for concurrency |
This could be somewhat related to #155 ? |
Describe the bug: Always docker overlay2.size and not pvc request size.
Expected behaviour: The actual size should be the pvc request size.
Steps to reproduce the bug:
openebs localpv and docker in same xfs with prjquota enabled
enable overlay.size in docker daemon config
The output of the following commands will help us better understand what's going on:
kubectl get pods -n <openebs_namespace> --show-labels
kubectl logs <upgrade_job_pod> -n <openebs_namespace>
Anything else we need to know?:
Add any other context about the problem here.
Environment details:
kubectl get po -n openebs --show-labels
): 4.0.0kubectl version
): v1.28.7+k3s1cat /etc/os-release
): ubuntu 22.04uname -a
): 5.15.0-97-genericThe text was updated successfully, but these errors were encountered: