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
I have been using PVC in a pending state during deployment, and the error message is:
I0929 07:14:15.076543 1 controller.go:1102] Final error received, removing PVC f3827433-97db-47c3-940f-c417da9866ff from claims in progress
W0929 07:14:15.076582 1 controller.go:961] Retrying syncing claim "f3827433-97db-47c3-940f-c417da9866ff", failure 4
E0929 07:14:15.076629 1 controller.go:984] error syncing claim "f3827433-97db-47c3-940f-c417da9866ff": failed to provision volume with StorageClass "csi-s3": rpc error: code = AlreadyExists desc = Volume with the same name: test1 but with smaller size already exist
I0929 07:14:15.076660 1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"csi-s3-pvc", UID:"f3827433-97db-47c3-940f-c417da9866ff", APIVersion:"v1", ResourceVersion:"342043136", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "csi-s3": rpc error: code = AlreadyExists desc = Volume with the same name: test1 but with smaller size already exist
I0929 07:14:31.076913 1 controller.go:1335] provision "default/csi-s3-pvc" class "csi-s3": started
I0929 07:14:31.077160 1 event.go:282] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"default", Name:"csi-s3-pvc", UID:"f3827433-97db-47c3-940f-c417da9866ff", APIVersion:"v1", ResourceVersion:"342043136", FieldPath:""}): type: 'Normal' reason: 'Provisioning' External provisioner is provisioning volume for claim "default/csi-s3-pvc"
My storage class file is:
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: csi-s3
provisioner: ch.ctrox.csi.s3-driver
reclaimPolicy: Delete
#volumeBindingMode: WaitForFirstConsumer
parameters:
mounter: s3fs
bucket: test1
# 'usePrefix' must be true in order to enable the prefix feature and to avoid the removal of the prefix or bucket
usePrefix: "true"
# 'prefix' can be empty (it will mount on the root of the bucket), an existing prefix or a new one.
prefix: ""
csi.storage.k8s.io/provisioner-secret-name: csi-s3-secret
csi.storage.k8s.io/provisioner-secret-namespace: kube-system
csi.storage.k8s.io/controller-publish-secret-name: csi-s3-secret
csi.storage.k8s.io/controller-publish-secret-namespace: kube-system
csi.storage.k8s.io/node-stage-secret-name: csi-s3-secret
csi.storage.k8s.io/node-stage-secret-namespace: kube-system
csi.storage.k8s.io/node-publish-secret-name: csi-s3-secret
csi.storage.k8s.io/node-publish-secret-namespace: kube-system
How to deal with this kind of problem?
The text was updated successfully, but these errors were encountered:
I have been using PVC in a pending state during deployment, and the error message is:
My storage class file is:
How to deal with this kind of problem?
The text was updated successfully, but these errors were encountered: