aws-efs-csi-driver: Failed to locate a free GID
/kind bug
What happened? Failing to create volume due to error “Failed to locate a free GID for given the file system”.
What you expected to happen? our storage class has the parameters
gidRangeEnd: "2000"
gidRangeStart: "1000"
However, we do not have 1000 volumes. We do how ever delete and create pvc a lot. When deleting the pvc and the pv should the gid be removed from the heap?
How to reproduce it (as minimally and precisely as possible)? my guess is to set that range rather small and create and delete volumes.
Anything else we need to know?: Our workaround was to delete the storage class and update with a new range. Then restart the controller pods
Environment
- Kubernetes version: eks 1.17
- Driver version: 1.2
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 21 (6 by maintainers)
Actually ,even if there were an exploit to look at parent directories, I thought the point of efs access points is there is no notion of parent directory in the first place, i.e. to the user of B it looks as though B is the root of the file system and there is no way it can access the parent, much less A.