You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if I create pv with the manual way as follow apiVersion: v1 kind: PersistentVolume metadata: name: manualbucket-with-path spec: storageClassName: csi-s3 capacity: storage: 10Gi accessModes: - ReadWriteMany claimRef: namespace: kdxe-system name: csi-s3-manual-pvc csi: driver: ru.yandex.s3.csi controllerPublishSecretRef: name: csi-s3-secret-other namespace: kdxe-system nodePublishSecretRef: name: csi-s3-secret-other namespace: kdxe-system nodeStageSecretRef: name: csi-s3-secret-other namespace: kdxe-system volumeAttributes: capacity: 10Gi mounter: s3fs options: volumeHandle: doris-kdxe
attention: the account in the csi-s3-secret-other is different from the acount in the values.yaml,as follow
so it cause an error beacuse of the different account。In the Daemon Pod(csi-s3-driver) show the error message,
failed to set internal data for access key/secret key from passwd file.
I thank, the account first write in the .passwd-s3fs is minio:123456789,after change the account (test:test),finally the .passwd-s3fs file content is test:test56789。so this case the s3fs command error。
The text was updated successfully, but these errors were encountered:
if I create pv with the manual way as follow
apiVersion: v1 kind: PersistentVolume metadata: name: manualbucket-with-path spec: storageClassName: csi-s3 capacity: storage: 10Gi accessModes: - ReadWriteMany claimRef: namespace: kdxe-system name: csi-s3-manual-pvc csi: driver: ru.yandex.s3.csi controllerPublishSecretRef: name: csi-s3-secret-other namespace: kdxe-system nodePublishSecretRef: name: csi-s3-secret-other namespace: kdxe-system nodeStageSecretRef: name: csi-s3-secret-other namespace: kdxe-system volumeAttributes: capacity: 10Gi mounter: s3fs options: volumeHandle: doris-kdxe
attention: the account in the csi-s3-secret-other is different from the acount in the values.yaml,as follow
![image](https://private-user-images.githubusercontent.com/8703812/390720347-0cfb5125-6680-4dd6-b2b9-4f09198c0dca.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNTQ1ODQsIm5iZiI6MTczOTE1NDI4NCwicGF0aCI6Ii84NzAzODEyLzM5MDcyMDM0Ny0wY2ZiNTEyNS02NjgwLTRkZDYtYjJiOS00ZjA5MTk4YzBkY2EucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIxMCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMTBUMDIyNDQ0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MDlkNmM1YjdmMmMyMDU1Mjg5YmQ4ZmI2NzlkNDNiYTFiOTEwMDE2MDFkYTFkZDlmNmYwY2ZjYjc0ZDM5YzM4NiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.leaR6-U0Letc-ikM7Hd1hsZO6FCqHf2de8nGj9MHbV4)
so it cause an error beacuse of the different account。In the Daemon Pod(csi-s3-driver) show the error message,
failed to set internal data for access key/secret key from passwd file.
I thank, the account first write in the .passwd-s3fs is minio:123456789,after change the account (test:test),finally the .passwd-s3fs file content is test:test56789。so this case the s3fs command error。
The text was updated successfully, but these errors were encountered: