Open
Description
version: v1.2.0-rc.2
kubernetes version: v1.23.17
mounter: s3fs
We use this version to mount Minio S3. But when we used different passwords to mount, we found the problem of mounting errors:
software caused connection abort。
K8s events :
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal SuccessfulAttachVolume 25s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-7f5e238b-fe55-4014-840f-ac88498ebe91"
Warning FailedMount 2s (x6 over 18s) kubelet MountVolume.SetUp failed for volume "pvc-7f5e238b-fe55-4014-840f-ac88498ebe91" : rpc error: code = Unknown desc = stat /var/lib/kubelet/pods/dc4e633a-9e8a-4abf-8d22-c795e629da45/volumes/kubernetes.io~csi/pvc-7f5e238b-fe55-4014-840f-ac88498ebe91/mount: software caused connection abort
By querying s3fs commands and csi-s3 source code,We found differences between csi-s3 password files and manual mounting methods
csi-s3 container : password file (/root/.passwd-s3fs) in csi-s3-nfb2x
manual write passoword file
so we guess password file is wrong , and we change password file (/root/.passwd-s3fs) in container csi-s3-nfb2x
mv .passwd-s3fs .passwd-s3fs_bak
echo minioadmin:minioadmin >> .passwd-s3fs
chmod 600 .passwd-s3fs
Afterwards, the mount was successful, and our deployments was also able to run successfully。
We are going to submit a PR to solve this problem。
Metadata
Assignees
Labels
No labels
Activity